CVS conflict avoidance

[Lassi A. Tuura]

I wonder if it was possible to hack the CVS repository setup at cygnus
such that *CVS* would regenerate `*-parse.c' (or similar) whenever
somebody commits in a change to any of the relevant source files.  Sort of
like how the files in CVSROOT are kept current.

I can see two potential flaws in this scheme: nothing guarantees that the
generated file compiles correctly, and the corresponding file in my source
tree would not reflect the version in the repository unless I would do
`update' immediately after the commit.  Perhaps these two can be worked
around?

//lat
--
Lassi.Tuura@cern.ch          There's no sunrise without a night