[Top][All Lists]

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

RE: Repository permissions

From: Tumy, Brad
Subject: RE: Repository permissions
Date: Wed, 14 May 2003 09:44:31 -0400


We have a similar setup...

At $CVSROOT we did the following
chmod g+s repository_name

this forces any check-in to the repository to have the same group as the
top-level of the repository.  I would presume that if you did that command
at the module level you could have different groups per module (never tested
that so I don't know).  

-----Original Message-----
From: David Bowring [mailto:address@hidden
Sent: Wednesday, May 14, 2003 5:02 AM
To: address@hidden
Subject: Repository permissions


I am running several projects in one central CVS repository on a linux
system.  I am using unix groups to separate those projects to the
developers who are permitted to work on them... This works fine until I
have a developer who is a member of multiple groups add a file to the
repository.. in this case it is added under is primary group (as you
would expect) and not under the group for that project (as would be
desired).  Once this is done, for developers who are not part of both
groups, checkout fails.  
At the moment I just do a chgrp -R periodically on that project and this
is generally sufficient, but as the projects become busier, its getting
difficult to keep up with the changes.  Is there a better way to achieve
what I am trying to do.



Info-cvs mailing list

reply via email to

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