Ed (et al)
VSS Pro:If your client is died in the wool dedicated to Microsoft
environment and Visual Studio IDE and MS2k,MS2003 servers then VSS makes
sense
VSS Con: Keep in mind it is a fairly useless code control when ported to
Unix or Mac..the reliance on NT attributes and file permissions is pervasive
CVS Pro: Works everywhere and supports ssh ..login in once using ssh and you
can update, delete or whatever..branch and merge work great
CVS Con: The files of a cvs client can be manipulated thru regular shell
commands e.g. rm -rf filename.ext removes the file (and cvs loses it as
well)
(if you're using CVS on a Unix box with lots of admins floating about..be
safe take a backup every night)
My 2 pennies/HTH
Martin-
----- Original Message -----
From: "Ed Griebel" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Friday, September 16, 2005 11:22 AM
Subject: Re: [OT] SCM stories (war? horror?)
VSS- walk away, don't make eye contact :-)
Pros: umm, it does manage versions, close integration with MS VisualStudio
Cons: windows-only administration and probably access too, not
intuitive to use, opaque binary files having no discernable relation
to the actual artifacts themselves, not cheap to buy although most do
not buy a license for every developer. The biggie though, sometimes
the database will get corrupted and you will have to restore your
repository from backup, although this may have been fixed.
CVS-
Pros: simple model for developers to understand how it works, changes
can be made to local version without locking a file (some would
consider this a con, so it can be changed), integrated into almost any
open-source IDE and many OSS applications (such as cruise-control),
trivial to access remote repository from local desktop, repository
artifacts are stored as "regular" files rather than an opaque
binary-format file
Cons: directories not versioned, file moves are not versioned so if
you want to preserve file history you have the hack of copying the
file to the new location in a repository, and binary file versioning
is non-existant--it stores a full copy of each version
No experience with perforce.
By the way, what is your current SCM?
-ed
On 9/16/05, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
I'm preparing to make a case for switching to a differenct SCM tool
(source code management). The options are CVS, Perforce, and VSS.
Anybody have any cogent/credible stories or arguments for choosing one
over the other?
Thanks,
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
