On Nov 7, 2003, at 12:21 PM, Kevin Meinert wrote:
> One advantage (only one I can see) is that VSS manages binary files
> well,
> i.e. it has exclusive locking. For this reason I would choose it over
> CVS
> or subversion at this point, though SVN will have it after 1.0.
I think Perforce would be a much better choice than VSS. Perforce
operates almost exclusively on exclusive locking, although you can
graft CVS-style merges onto it with external tools. Perforce may be
expensive, though.
Chris
>
> CVS has advisory locks, but might not be what you want (I know I don't)
> for a large organization.
>
> If you have binary data, be sure that your source control can manage
> it.
> Exclusive locking is nessesary to prevent two people updating the same
> file at the same time - which then requires they hand merge changes.
> This
> is really really hard for some data formats (3d models with animation,
> texture mapping, etc.. for example).
>
>
> On Fri, 7 Nov 2003, Sir Woody Hackswell wrote:
>
>> On Thu, 6 Nov 2003, Wadsworth, Eric (Contractor) wrote:
>>
>>> In other words, they are choosing it kind of by default. They have
>>> not
>>> considered features in their choice. The people I spoke with said
>>> that they
>>> would be open to consider alternatives to VSS. Now would be the time
>>> to
>>> clear my throat and say something, if something will ever be said
>>> here.
>>>
>>> I, for one, have never seen VSS used, but one guy on my team here
>>> says he's
>>> used it, and hated it. Has anyone writtem a document doing a feature
>>> comparison? How about a usability comparison? Is there a URL that
>>> compares
>>> Subversion with VSS, showing relative strengths and weaknesses? I'd
>>> like to
>>> have a document to pass around to a few key people (some of whom are
>>> big
>>> open-source fans) but I'm not qualified to write it myself, having
>>> never
>>> used VSS.
>>
>> I'll vouch for the crappiness of VSS. It corrupts easily, and the
>> tools MS
>> gives you to fix it, don't fix it. =sigh= It also gets very very slow
>> as the
>> database gets larger. No atomic commits. You must lock files to
>> edit them.
>> NO UNIX SUPPORT. About its only advantage that we use is file
>> "sharing"
>> between projects. i.e. you update a shared file in one project, and
>> someone
>> checks out the other project, they'll get the same version.
>>
>> I'd even consider CVS over VSS any day.
>>
>> A few comparisons:
>> http://www.perforce.com/perforce/reviews.html
>> http://better-scm.berlios.de/comparison/comparison.html
>>
>> One in Italian, if you read it:
>> http://www.siforge.org/articles/2002/12/10-version-control.html
>> Google translated version:
>> http://translate.google.com/translate?hl=en&sl=it&u=http://
>> www.siforge.org/articles/2002/12/10-version-control.html&prev=/
>> search%3Fq%3DVSS%2Bsubersion%26hl%3Den%26lr%3D%26ie%3DUTF
>> -8%26oe%3DUTF-8
>>
>>
>> -Woody!
>>
>> -----
>> veni, vidi, vomi
>>
>> Sir.Woody_at_Hackswell.com http://sir.woody.hackswell.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>>
>
> --
> *--*---*---*----*-----*------*------*-----*----*---*---*--*
> Kevin Meinert /_/
> home - http://www.vrsource.org/~kevin \ /
> music - http://www.subatomicglue.com \/ __ \/
> \__
> \_\
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 8 00:08:16 2003