Re: disable cvs commit and/or make repository read-only

[Todd Denniston]

Robert Dodier wrote:
> Hello,
>
> I am considering converting an existing CVS repository to Subversion.
> After that I'd like to make it impossible to commit stuff to CVS
> to avoid heartbreak, confusion, etc.
>
> What is the standard practice for making a CVS repository read-only?
>
> I've searched this ng for ideas and didn't come up with anything clear
> to me.
> One idea was to modify the file system permissions but wouldn't
> it be better to do it through CVS itself? (Instead of letting CVS try
> to commit stuff and fail.)
>
> Anyway I welcome your comments.

permissions most of us understand, and I think could be made to work easily
and quickly, so it is usually the best route.

A second route would be to use a:
commitinfo script returning non-zero, i.e. in commitinfo config file put the
following line:
ALL false

taginfo script returning non-zero, i.e. in taginfo config file put the
following line:
ALL false

AFAIK this should prevent them from committing or tagging, and if you combine
it with making all the directories read-only you should have a fairly good
defense setup.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter