[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple developers in one work area

From: Noel L Yap
Subject: Re: Multiple developers in one work area
Date: Thu, 21 Dec 2000 10:02:25 -0500

I've been trying to get our developers to do the following:

Each developer works in their own working directory.
When they're ready to test their work, they install it into a common area (eg
doc root).
To help prevent developers from stepping on each other, files are installed as
group read only.
To prevent developers from blocking each other, directories in the common area
are group writable.


address@hidden on 2000.12.14 18:46:15

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  Multiple developers in one work area


  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?


Parand Tony Darugar

Info-cvs mailing list

This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]