making a read-only module in a read/write repository

[Adam Mercer]

Hi

We have a CVS repository containing many modules and I need to make a
couple of these modules read-only but maintain read/write access for
the other modules in the repository. I have tried simply changing the
permissions of the modules on the server to read only but this leads
to failure in creating read locks.

Another option is remove the write bit from each of the ,v files, yet
this will still allow new files to be created in the module.

Is there a way to specify a writers/readers file on a per module basis?

Cheers

Adam

[Adam Mercer]

Post by Adam Mercer
Another option is remove the write bit from each of the ,v files, yet
this will still allow new files to be created in the module.

I did this and yet as user was still able to commit, surely there must
be a away to make a module read only. I've been through the manual and
can't find anything. Google yields no results either. Anyone?

Cheers

Adam

[Jim Hyslop]

Post by Adam Mercer
We have a CVS repository containing many modules and I need to make a
couple of these modules read-only but maintain read/write access for
the other modules in the repository. I have tried simply changing the
permissions of the modules on the server to read only but this leads
to failure in creating read locks.

You're on the right track. Make the modules read only, and add the
"Lockdir=somedir" setting to the config file, where "somedir" is a path
to a writable directory. See Appendix C.11 in the manual for more details.

- --
Jim Hyslop
Dreampossible: Better software. Simply. http://www.dreampossible.ca
Consulting * Mentoring * Training in
C/C++ * OOD * SW Development & Practices * Version Management

[Todd Denniston]

Post by Jim Hyslop

Post by Adam Mercer
We have a CVS repository containing many modules and I need to make a
couple of these modules read-only but maintain read/write access for
the other modules in the repository. I have tried simply changing the
permissions of the modules on the server to read only but this leads
to failure in creating read locks.

You're on the right track. Make the modules read only, and add the
"Lockdir=somedir" setting to the config file, where "somedir" is a path
to a writable directory. See Appendix C.11 in the manual for more details.

IIRC, you can also achieve the effect desired with the cvs_acls script from
the contrib directory.

Perhaps look at using both for a second line of defense. :)

[Adam Mercer]

On Wed, Apr 1, 2009 at 06:47, Todd Denniston

Post by Todd Denniston
IIRC, you can also achieve the effect desired with the cvs_acls script from
the contrib directory.
Perhaps look at using both for a second line of defense. :)

With our users that's definitely a good idea :-)

Cheers

Adam

[Adam Mercer]

Post by Jim Hyslop
You're on the right track. Make the modules read only, and add the
"Lockdir=somedir" setting to the config file, where "somedir" is a path
to a writable directory. See Appendix C.11 in the manual for more details.

Fantastic, I can't believe I missed that. Thanks.

Cheers

Adam