Re: Multi-user working directories

[Alex Holst]

Quoting address@hidden (address@hidden):
> Thank you.  Yes I do know about branches and merging branches.  How does this
> solve my problem?
> 
> I need to create a set of binaries from our GA branch.  The GA branch has been
> checked out and built previously (the "Official Release" files).  The question
> is how do I have any person (one of our Level 3 staff) be able to update the
> "official release" set of working files with the updates everyone has been
> working on and then do the build.

Your 'binaries' statement confused me for a moment. I will assume we are not
actually dealing with binary files, but text files of some sort, that CVS
understands how to handle in an acceptable manner.

_I_ would checkout the 'Official release', possibly make whatever changes
and tag them with a meaningful name. Then I would tell others which tag to
checkout and commit to. The release could be tagged according to the
deadline, eg FEB12_2001.

OpenBSD does this. They have a tag named OPENBSD_2_8 to which they apply
critical fixes for OpenBSD 2.8. This is a live tag that changes, so all
administrators have to do is checkout that particular tag to get the stable
release. The code that is shipped on the CD is tagged OPENBSD_2_8_BASE.

> UNIX (or in our case USS on MVS) will allow multiple people write access to
> these files, but CVS (specifically pserver) will not.

CVS has no concept of access control lists. This would be implemented
through filesystem permissions. Ensure the people who need to commit changes
to a directory has sufficient rights. Once you solve this problem, you can
apply your knowledge of branches to the problem.

-- 
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow.