I posted a new version of cvs_acls to this mail group later in the day. It is called cvs_acls2. It addresses the problem you mention by (optionally) allowing you to specify the client-side userId in the commitinfo file so that access is controlled by the client-side userId, not the pserver server-side userId.
Hope that helps. pc > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:info-cvs- > [EMAIL PROTECTED] On Behalf Of Mohamed Eldesoky > Sent: Thursday, February 26, 2004 1:38 AM > To: CVS > Subject: cvs_acl and cvsd > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > I am preparing a CVS server for my organization, and I am using cvsd and > at > the same time I want to use cvs_acl to determine who has access to what. > > Alas, it doesn't work, because it treats all users as if they are (cvsd) > user !! > > Anyone succeeded to overcome this ?? > > I know this is not the place to ask this question, but I searched alot in > google, and I hope someone here has solved this before. > > Regards > Mohamed Eldesoky > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQFAPb5r2FHsOWMJBKMRAkTkAKDBPusumJOk6WCzKTkuW0CoKXRWzwCgm5jS > 4ZKb69cWCr2GYwcfW0uJGQM= > =kBmo > -----END PGP SIGNATURE----- > > > _______________________________________________ > 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
