Hello,

  I'd like to setup CVS for a web based project
that involves multiple developers. We would like 
to have those multiple developers access the
same directory of source code, as opposed to each
having their own working area. The reason behind this
is that everyone needs to use the same web server
for testing, and hence the same working area.

  In traditional situations, each developer is able
to build and test the project in their own working
area. With the web based project, there is no build
process as such, and testing requires a fairly complex
setup. Therefore, we would like to share a common code
area, and access the files with RCS locking style to
avoid trampling on each other's work.

  Why not just use RCS? CVS offers better branching
facilities, as well as better web integration, etc.

  Given that scenario, can CVS be used? I'd like the
files to be read-only, and made available for editing
only after a "cvs edit". This works fine with "watch on",
but when the second developer tries to "cvs edit" files
we run into permission problems, since the files are
owned by the 1st developer.

  I've tried playing with permissions, but haven't hit
a combination that works. Any ideas?

Best,

Parand Tony Darugar

_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to