httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Behlendorf <>
Subject CVS modules
Date Fri, 05 Dec 1997 22:29:55 GMT

I'm going to sit down and add a couple new modules to the CVS repository on, first for mod_perl, and then if the mod_jserv folks are
interested, one for them.  Since I think we'll want to allow different
write access controls across these modules, yet keep some level of
consistancy in CVS services, I'm going to implement it according to
Alexei's recommendations.  if you see some weird messages to apache-cvs or
even new-httpd, that's me banging around.  Let me know if you see any
problems with this approach, or with CVS in general.


Alexei wrote:
>A while ago, Brian Behlendorf wrote:
>> Before I begin; it pretty much sounds like the only way to do this is to
>> give each CVS repository its own UID, as well as its own CVSROOT directory.
>>  Let me know if I'm wrong.
>No, not neccessarily. The $CVSROOT and $CVSROOT/CVSROOT directories have
>to be owned by someone who's trusted by all parties, or actually root
>(because of the security bug with pserver), but each module can be given
>write permission for the user/group responsible for it, and not
>others. It just needs a central person (i.e. Brian) to add new
>modules/change CVSROOT stuff, but due to the pserver bug, that's needed
>The only issues then (I think) are commit privs and cvs mailings. You can
>set up avail by module if you want:
>This gives brian and akosut commit access to the apache and apache-docs
>modules, and dougm commit access to the perl module. So that solves that
>problem. However, you'd have to modify to allow you to
>specify $MAIL_TO by module.
>Or you could just set up a different repository for each project. That'd
>work, too.
>-- Alexei Kosut <>
"it's a big world, with lots of records to play." - sig

View raw message