[Users] CVS Repos

[Tom Goodale]

Hi,

with CVS the only way we found to do this was to use filesystem ACLs to 
only give write access to directories to people who could check out from 
there - CVS writes a lock file so preventing write access prevents them 
being able to use CVS to read from a directory.

For check-in access, we use the cvs_acl. perl script available in the CVS 
tarballs to restrict access.

I.e. we use filesystem ACLs to restrict read access, and the cvs_acl 
script, invoked from the commitinfo file in the CVSROOT, to restrict 
check-in access.

Cheers,

Tom

On Tue, 19 Sep 2006, Giovanni Corvino wrote:

> Hi everybody,
>
>
> We're setting up a CVS repository here in Parma, to manage the
> developments of our codes. In our minds it should work just as
> Cactus one (except for the fact that it will be several orders of
> magnitude smaller). Our problem is that we can't give priviledges on a
> user basis for different modules in the repository. Is there anything we
> can do to solve this problem? We found lots of HOWTO on the net
> but they're not clear about this point so, maybe any of you can make
> some suggestion, I'm sure it would be very useful.
>
> Thanks a lot,
>
> Giovanni Corvino
>
> _______________________________________________
> Users mailing list
> Users at cactuscode.org
> http://www.cactuscode.org/mailman/listinfo/users
>