CVS event mechanism?

[Andrew Gilmartin]

Has there been any proposals to add an event handling mechanism to CVS much
like there is in Apache? (Apache allows your to associate code to any of the
stages of its processing of a web request. This powerful mechanism allows
you to redirect and or modify Apache's default response to the request.) CVS
has a little of this today with the loginfo, commitinfo, etc handlers. Over
the last several days I have needed 1) to tag files as they are committed
and 2) add the recent "list" patch. The first was accomplished with
information from the FAQ
(http://cvshome.org/docs/manual/cvs_18.html#IDX538), but I really can't
trust it (due to race conditions) and the second was accomplished by
patching and rebuilding CVS. This seems like the wrong way to enhance my
organization's use of CVS. I would rather take a prebuilt CVS and then
configure it to 1) run CHECK_TAG.pl before a commit and ADD_TAG.pl after a
commit and 2) dynamically load the LIST module. I suspect that if such a
mechanism existed it would not be long before we have a mod_perl, mod_tcl,
mod_snake scriping modules.

---
Andrew Gilmartin
Mesa Systems International
address@hidden
401-828-8500x128