Jim Hyslop wrote: > > S I wrote: > > Hi Class! > > > > Currently our CVS repo has 3 main & separate projects running under it. > > By default when I create a new unix user; I give them access to the > > whole repository, however, some folks have been editing files in > > projects they were not supposed to. > > > How can I ONLY and specifically create or modify the access rights & > > privileges of only few specific people w/o wreaking havoc on the whole > > repository? And by default if they're not listed in that file then that > > means they have access to all projs? Is there a way? > > Use your operating system's access control system. Create a group for > each project, and assign people to the groups they are allowed to be in. > You will have to determine, in conjunction with your project leaders, > which projects new users will have access to, by default. > > And, of course, get the managers and project leaders on side to explain > that changing project files they haven't been assigned to will result in > disciplinary action, up to and including termination.
Although the above is what I also see as the best option, you *MAY* also be able to get some where in the middle using the cvs_acls script. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
