Unfortunately, with programming teams of a few or more,
it becomes very difficult to maintain control of the code,
and without a system such as this, there will usually be
lost code due to 2 or more people modifying a piece of
code at the same time, and not coordinating properly. CVS
et al handle this coordination for you really well.

There are 2 general flavors of SCCSes (Source Code Control
Systems) that I've run into ... the library system (such as
CVS) and the versioning system (such as Envy). The first
let's one person check out a file at a time while others can
only have it read-only. The other lets multiple people have
write access, but will put a separate version ID on each in a
special format, so that it is evident at build/compile time
that multiple changes had been made and need to be
merged". Each has its pros & cons.

In any programming team, the server is usually local to the
group, so it's not a big security issue. And one DB for all
code makes backups sooooo much easier and transparent.

Cheers,
-Neil.



-----Original Message-----
From: Lawrence Lile <llile@TOASTMASTER.COM>
Organization: Toastmaster Inc.
Subject: Re: [PIC]: coding style
To: PICLIST@MITVMA.MIT.EDU


Yow! - CVS looks complex and smells like it has security issues. Do I
understand correctly that it stores your project documents on somebody
else's server? This gives me the shivers. If I was doing a far-flung GNU
project with a bunch of volunteer programmers this might be a good system to
use.
I think I'll stick to revision notes at the beginning of my C source file,
that's pretty simple.
--Lawrence

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body