There's another approach to controlling access to directory *and files* that is in the 'contrib' subdirectory. It's a script called cvs_acls that provides access control lists for your repository. It avoids the increasing nastiness (IMO) of having to juggle an ever-expanding list of *nix groups to match the different access requirements to your repository. That is the inevitable end-game of the approach described in <http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_2.html#SEC13>.
Having said that, I ran into some problems using the original script. There were some bugs and some not-so-nice features. As a result, I rewrote the script last month. The new script's name is cvs_acls2. I submitted it to the ccvs project this month for regular inclusion in its distribution. I think you may find it useful. I've added the script and its documentation into the issues log on the ccvs project Issuezilla: <http://ccvs.cvshome.org/issues/show_bug.cgi?id=170> pc > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Sandhya > Sent: Thursday, March 25, 2004 1:32 AM > To: [EMAIL PROTECTED] > Subject: folder level access in cvs > > > Hi all, > > Joining new to the team of mails... > Have started to be the admin of cvs for for the past 1 month. > Just wanted to know how to give read- > write access on a folder level in cvs. > I have tried readers and writers. but that works only for > repository level and not for modules or > directory level. If anyone can help me out how this can be > achieved, it wud be of great help to me. > > Thanx in advance > Sandhya.S > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
