Re: Multiple developers in one work area

[Pascal J. Bourguignon]

I think that  it would be better  to use RCS in that  case. By default
CVS does  not require  a lock to  modify a file,  therefore developers
would be able to do changes to the same file and some work by be lost.

With RCS, by default, you have to do a check-out to be able to work on
a file.

With CVS, you can put locks on files too, but it's not the natural way.

In  any  case, beware  of  doing  tests  using "sources"  files  being
edited. While I edit a file, I  save it often, and most often, it's on
the disk in  a non-compilable (non-usable) state. To  do your tests in
your environment, all your developers should stop edit all their files
at the same time, and will be blocked while you do the test.


That's why, even  in your case, it would probably  better to give each
developer a separate "editing"  directory, using CVS normaly, and have
one more directory for the test environment where you'll be able to do
checkouts or updates at any time in a controled way.


-- 
__Pascal Bourguignon__    PGP Key ID:      0xEF5E9966
mailto:address@hidden    PGP fingerprint: 00 F5 7B DB CA 51 8A AD 04 5B 
http://informatimago.free.fr/index         6C DE 32 60 16 8E EF 5E 99 66

() Join the ASCII ribbon campaign against html email and Microsoft attachments.
/\ Software patents are endangering the computer industry all around the world.
   Join the LPF:     http://lpf.ai.mit.edu/      http://petition.eurolinux.org/