I only learned about this by reading the docs on Savannah; the admins canprovide better information. But my understanding is simply that they haveM users and N projects, and they want the system to support any number ofpermission pairs from M x N, i.e. they want each user to be able to committo an arbitrary number of projects. And CVS relies on OS permissions.

> I saw the post about having to have access to a lock directory by a> cvsuser, but how is that different than having that directory with an> ACL entry that includes the cvsuser? Or an ACL that includes the> group that the cvsuser is a member of?

I guess they prefer to use traditional Unix permissions rather than ACLs.I have the same preference. Unix groups are well supported by tools andthe kind of permission setup I described above is nicely transparentto administer. Granting a user write access to a project is simply'adduser username projectname', and a project can easily support a largenumber of writers without big ACLs.

The issue is not just lock directories, but the right to change anyfile in a project, i.e. full CVS commit access to the project ratherthan anonymous access. So they would need an ACL on each file in therepository, and they would need new files to inherit ACLs from theirparent directories (I've never used ACLs on Linux but I assume this kindof thing is supported).