On Tue, Jan 28, 2003, Matt J. Gumbley wrote: > (We're using cvs 1.11.2 client and server, pserver, SystemAuth=no, we > have a UNIX cvs group containing all users, and all users are listed in > CVSROOT/passwd) > > Is there any way in which we can set up our repository with > access-control-list -like behaviour? > > e.g. We have several projects in our repository, called X, Y and Z. > These projects contain source code. We also have projects Xdoc, Ydoc, > Zdoc which are the documentation for the X, Y and Z projects. We have > modules in CVSROOT/modules of the same name, if that matters. > > We have several developers, and several technical authors. > > What we'd like to achieve is for the developers to have > checkout/read/write/commit access to X, Y and Z, and read-only access to > Xdoc, Ydoc, Zdoc, and for the authors to have checkout/read/write/commit > access to Xdoc, Ydoc, Zdoc, but no access at all to X, Y, Z. > > (I'm cvs admin; I'd like to do anything to any project)
Have a look at OSSP shiela (http://www.ossp.org/pkg/tool/shiela/). It can provide you flexible access control to modules based on user and groups. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
