CVS Repository Protection

[Sarang Padalkar]

For different users to be able to commit files, it seems like the CVS
repository needs to be world-writeable. We have had mishaps where 
users accidentally delete files from the repository

(eg. the cvs status command prints the absolute pathname of the
repository file. We've had users accidentally remove this file
because they cut and pasted it thinking that they were removing
the file from their workarea).

Is it possible to set CVS up so that the CVS repository is not
world-writeable? ie. some king of setuid script that performs
cvs operations with a different userid?

Thanks,
Sarang