From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Kurt Lieber <klieber@gentoo.org>
Cc: gentoo-dev@gentoo.org, robbat2@gentoo.org
Subject: Re: [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal
Date: Tue, 12 Aug 2003 14:56:47 -0700 [thread overview]
Message-ID: <20030812215647.GD31636@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20030812124513.GD4094@mail.lieber.org>
[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]
On Tue, Aug 12, 2003 at 08:45:17AM -0400, Kurt Lieber wrote:
> 1) I'd like Robin (robbat2) to comment on this since the primary reason for
> the GLEP seems to be better control over CVS permissions. I know Robin has
> some ideas on how he wants to change CVS permissions, so his feedback here
> is important. (cc'd on this email)
To elaborate on this, I planned to implement the same software FreeBSD
uses to help manage their CVS repository. It consists of a few files in
CVSROOT and changes to existing files there only. It changes us to using
an access control list (contained in files, not using filesystem ACLs)
from the existing UNIX permissions.
The documentation at the top of this file describes the system best.
http://www.freebsd.org/cgi/cvsweb.cgi/CVSROOT-src/cvs_acls.pl?rev=1.24&content-type=text/x-cvsweb-markup
Here is the 'avail' file for the FreeBSD 'src' tree:
http://www.freebsd.org/cgi/cvsweb.cgi/CVSROOT-src/avail?rev=1.208&content-type=text/x-cvsweb-markup
There is also a patch to the cvs_acls.pl program so that the directory
elements it takes can be regular expressions.
As a side bonus this would remove the nasty CVS locks that presently
occur when somebody tries to checkin some code to a place that they
don't have access to, and the lock gets left behind.
It also makes it very easy to specifically restrict any given user(s) or
group(s) from any given part of CVS, or vice versa, as an example:
unavail||gentoo-x86/sys-apps/portage,gentoo-src/portage
avail|carpaski|gentoo-x86/sys-apps/portage,gentoo-src/portage
This blocks anybody execept carpaski (and the cvsadmins as they would
have a later rule allowing them global access) from being able to modify
portage.
--
Robin Hugh Johnson
E-Mail : robbat2@orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-08-12 21:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 18:31 [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal Sven Vermeulen
2003-08-05 10:18 ` Svyatogor
2003-08-05 11:43 ` Sven Vermeulen
2003-08-05 11:50 ` FRLinux
2003-08-05 12:03 ` Svyatogor
2003-08-05 13:07 ` Sven Vermeulen
2003-08-12 13:05 ` Kurt Lieber
2003-08-12 13:20 ` Paul de Vrieze
2003-08-12 13:41 ` Sven Vermeulen
2003-08-12 15:56 ` Kurt Lieber
2003-08-05 13:31 ` Lisa Marie Seelye
2003-08-05 13:25 ` Svyatogor
2003-08-05 14:15 ` Paul de Vrieze
2003-08-05 15:21 ` Sven Vermeulen
2003-08-05 19:51 ` Paul de Vrieze
2003-08-06 8:06 ` Sven Vermeulen
2003-08-12 12:45 ` Kurt Lieber
2003-08-12 13:36 ` Sven Vermeulen
2003-08-12 13:43 ` Svyatogor
2003-08-12 21:56 ` Robin H. Johnson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030812215647.GD31636@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=klieber@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox