In that case, take a look at the -o and -u options that can be used in the modules database. These features are pretty gunky but they might fill the bill by allowing you to register programs to execute during checkout and update. The downside is that they drop cookies in your sandbox that can't be updated automatically.
--- Forwarded mail from [EMAIL PROTECTED] Arguably it _is_ for a build system to register libraries etc., but as I work in interpreted languages where the compilation is usually incremental (check out libraries+source, work on interpreted source using compiled libraries, compile everything for deployment), a 'build' system as such except for the specific case of deployment doesn't really make sense, since you usually compile about 20% of it. I would still like to tie 3rd-party operations into checking out files automatically, if possible. Can this be done using the existing admin files? --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
