Re: Locking CVS

[Todd Denniston]

S I wrote:
> 
> Hi everyone,
> 
> I'm planning to lock cvs today getting ready for our release.  I realize
> with certain version control software nowadays you don't have to lock the
> repo and the developers can continue with their work.  However, we're
> imposing and enforcing a few days for freeze and to regroup.

Another method would be to tag and then branch, decide whether the trunk or
branch is where you will host the release, and use cvs_acls to lock down the
trunk/branch for release work only. look at ACME [2] for ideas.

> 
> Our repository resides on a linux box with :pserver method access from WinXP
> CVS DOS and Tortoise clients.  Could I just lock the repo by executing cvs
> admin -l or -L  or do I have to download some perl module to accomplish
> this? I need to lock our CVS repository today.  Three projects reside in the
> repository, is it possible to lock them selectively or would admin -l lock
> the entire repo?
> 

There are  a few ways I think you could go at it.

If you don't even want anyone reading from the repo, you could temporarily
remove it's allow-root option from [x]inetd.conf.(assumes the three projects
have different roots in [x]inetd.conf)

if you are ONLY accessing the repo via pserver, the reader / writer [1]
files could do it for you.(assumes the three projects have different roots
in [x]inetd.conf, OR that none of the developers work on multiple projects)

if you want fine grain control, look at using cvs_acl, from the distribution
contrib directory, as a commitinfo script.

[1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36

[2] http://www.cmcrossroads.com/bradapp/acme/
    http://www.cmcrossroads.com/bradapp/acme/branching/

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter