Re: CVS event mechanism?

[Noel L Yap]

A work-around for the race condition:

I've been able to work around the race condition by creating temporary modules
within the repository that's populated by symlinks to the necessary archive
files from the real repository, using CVS operations on the temporary module,
then wiping out the temporary module.  Be warned, this is extremely slow (you
may find ways to speed it up though, eg, don't wipe out the temporary module at
the end and create symlinks only when necessary).

Aside from this, there has been sporadic talk of rearchitecting the hooks into
CVS operations, but I've seen nothing come of it.

Noel




address@hidden on 2000.10.23 13:14:43
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



_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.