[Top][All Lists]

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

Re: Read Only Repository, Sort of

From: Mark D. Baushke
Subject: Re: Read Only Repository, Sort of
Date: Fri, 16 Mar 2007 13:38:50 -0700

Hash: SHA1

Huber, Robert <address@hidden> writes:

> I have the requirement to make a read only repository for a legacy
> system and another to make a repository for a current system where
> individual developers can check out code but only the administrator can
> check the code back in. 
> Are either of these a practical option and if so how does one set up the
> permissions or do I have to develop a set of wrapper scripts to provide
> for this capability?

The CVSROOT/config file will want to use a directory other than the
repository and then you can make the read-only repository use a userid
and groupid for which no user of the repository has write access.

For the second case, you will need to make use of the commitinfo and
taginfo triggers to disallow users other than your administrator from
doing the modifications. This will not stop 'mkdir foo && cvs add foo'
operations, but as directories are not really revision controlled it
should not matter that much.

the contrib/cvs_acl* script in the CVS source distribution should be a
good starting place for the commitinfo scripts. The taginfo script will
probably have to be one you write yourself.

        -- Mark

PS: Tell your system administrator that appending their disclaimer to
outgoing email to large mailing lists that are archived automagically in
many place makes the company look like they have cluseless/silly
individuals running their company.
Version: GnuPG v1.4.6 (FreeBSD)


reply via email to

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