Steve Williams wrote:
> William Nagel wrote:
>
>> Not to sound negative, but I really think (safely) converting an SVN
>> repository to a VSS repository by Tuesday is going to be a Herculean
>> effort, and I doubt you're going to find many people on this list
>> willing to put in much effort to help you, as there just isn't much
>> interest out there in going from SVN to VSS, nor does anyone want to
>> deal with VSS for anything other than getting away from it. I know
>> that I personally wouldn't subject myself to undertaking such a
>> project even for large amounts of cash.
>
>
> The original post mentioned "VSS 2005" several times. I'm wondering
> if he means the replacement for Visual SourceSafe that isn't
> officially released yet. If so, then "Herculean" would be optimistic
> since the chances migration to an unreleased system are almost nil
> because not many people have used it yet.
No, there actually *will* be a VSS 2005, and believe it or not, they are
actually fixing many of the bugs that have plagued it for a long time.
I've downloaded the code and played with it a bit; the API actually
seems to be fully implemented now.
Of course, it's still VSS with all its limitations... 4GB repository
size limit (that alone should scare away any serious enterprise user),
no true client/server architecture, "security" is merely
smoke-and-mirrors around a world-writable file share (what's the point
of restricting access in the GUI when I can log in and delete or
reverse-engineer all your files?), etc. etc. etc.
You are no doubt thinking of Visual Studio Team System, which is an
entirely different beast and which encompasses much more than version
control. I'm sure it'll cost quite a few appendages and firstborns.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 05:01:28 2005