[EMAIL PROTECTED] on 04/14/2000 03:23:54 AM >I'm not sure if I understand your problem right, but maybe this helps. >CVS allows to maintain a checked out copy of the latest version in the >repository via a loginfo script. Look at chapter C.7.2 of the Cederqvist >Manual: Keeping a checked out copy. Every developer only needs to check >out the files (s)he wants to modify. The only thing you have to do is to >configure your development tools so that they search for the files in that >directory of they are not found in the developers working directory. >With a more sophisticated script it should be possible to maintain copies >of branches, too. The downside to this is that everyone is affected by everyone's changes. An alternative is to have periodic stable versions. Each stable version is checked out for others to link to. A home-grown tool can: 1. Link to the user-specified version and maintain a count upon checkout. 2. "cvs checkout" and "cvs edit" files upon edit. 3. Relink the files upon an unedit (via an actual unedit command, commit, or release). 4. Remove the link and decrement the counter upon release. 5. Remove the copy when the count hits zero (you may decide to do cleanup some other way). Of course, the above is extremely preliminary -- there's a lot of detail missing that'll affect the final tool. Noel
