CVS and policy control

[Johnson, Susan]

I am trying to find out how to handle policy control
within CVS at the server level, just like the pre-op
and post-op triggers within ClearCase.

I have read about the files:
loginfo
taginfo
rcsinfo
editinfo
commitinfo

Can I modify taginfo to prevent deletion of branch tags
and moving of tags (labels) that I created for baseline
labels?

Can I modify commitinfo to prevent checkin to the main
trunk (we use main for the Production branch and all
the developers work on side branches)?

Can I modify commitinfo to prevent deletion of files 
from the repository?

Also, do I modify CVS so that nobody else but myself can
modify those *info files. and if so, how?

Lastly, is there a way to modify ownership and permission
of the files in the CVS repository so that they are owned
only by the CVS administrator (similar to a post-op 
checkin trigger in ClearCase)?

Thanks.

Susan