>Thomas Raschbacher wrote:
>
>> > If anyone wants to manage the docs tree, be my guest! :^)
>
>> I'll do that if you want me to.
>
>Sounds good to me.
>
>Anybody, is it possible to give CVS write permission to
>someone, but limit the scope to a directory downward?
>
>This would be ideal for stuff like docs management,
>and other subprojects.
Ok, I take back what I said before about seeming to not be able to do it,
althogh it's a bit of a hassle. You can play a neat little game (which I
just did) with the $CVSROOT/CVSROOT/passwd file (simplified, obviously):
nbastin:CrYpTsTrInG:nbastin
guest:cRyPtStRiNg:cvsguest
Ok, the first column is the cvs username. The second column is, obviously,
the password, and the third column is the user in the /etc/passwd file that
this user relates to. You can now play a neat game with /etc/group to put
certain users in a group called docs, and then make all of the files in the
docs tree have permissions of 775, and then make docs the group, and then
every user in the docs tree can write, but people in other groups can only
read. This works out well, obviously, since people can belong to more than
one group. However, all this said, you have to be careful to make sure
that if someone belongs to more than group, that the files they write in
docs/ are with a group ownership of docs, and not of their other group.
Ahh, unix. :-)
--
Nick Bastin
Software Developer
OPNET Technologies
