info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question on cvs acl options


From: Mark D. Baushke
Subject: Re: Question on cvs acl options
Date: Mon, 10 Oct 2005 12:49:52 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Abhilash Koneri <address@hidden> writes:

> We are using cvs on a fairly large site with pserver option. We create cvs
> users that are not system users and manage the module access using a number
> of system users. However, this makes access management somewhat difficult
> with growing number of projects and users. We have tried to use cvs_acl
> script, but we found that it uses the user name derived from the environment
> and not from the connection string passed through the :pserver option. Is
> there an option (compile time or runtime) that can be used to pass the user
> name in the pserver connection string to the pre-commit hooks ?

You should be able to use $CVS_USER environment variable that is passed
to the administrative files.

    http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_18.html#SEC183

Something like

    DEFAULT $CVSROOT/CVSROOT/cvs_acls -u $CVS_USER

should do the trick for you.

> We did modify the cvs source code of 1.11.20 to obtain the functionality
> needed. 

It should be available to you already without modification.

> (See the diff patch below). But we would like to know if there is a
> standard option already available for this. If not, would it be
> possible to include the same in the future builds as a compile time or
> runtime option?

If your server has a HAVE_PUTENV functionality, then CVS_USER should
get put into the environment for both :ext: and :pserver: mode.

If you are using a :local: repsitory, then it will not be available.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFDSsXfCg7APGsDnFERAhW/AKCEOh+r2ctOtw+TJVyIy4rB/Dud2QCeJZoy
f6lZ6nsAu3NUBYMJcQ+vkq4=
=+kC3
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]