Hi, I've searched for this issue on info-cvs, and haven't found it, though I
have seen similiar questions...
I have several projects on a Linux hosting box. I am not a superuser. I
have the following groups:
1. everyone
2. developers
3. clientA
4. clientB
5. clientC
Developers are part of all groups, ie:
sammy: developers everyone clientA clientB clientC
Clients have access to their own group & everyone:
joeA: clientA everyone
I want the following repository structure, with associated access:
/home/cvs/www/common (everyone)
/home/cvs/www/tools (developers)
/home/cvs/www/clientA (developers & clientA)
/home/cvs/www/clientB (developers & clientB)
/home/cvs/www/clientC (developers & clientC)
I've managed to do this, but I have this problem: whenever someone checks
in a file, the file's group changes to their primary group, so if a
developer checks in a file in "www/clientC", which is supposed to have a
group "clientC", the group changes to "developers" and locks out the client.
How can I get:
1. CVS to always use the permissions of the directory it's contained in
2. CVS to use the pre-existing permissions of the file, regardless of
check-in
I've thought of some commit scripts for this, but was hoping for something
easier.
Thanks in advance,
Tim
