> The goal would be to automatically commit updates to the generated
> files whenever there are changes to their predecessor files.
I use the commitinfo file to force developers to maintain it all by
hand. For example, here's a line from a commitinfo in one of our
repositories:
^conf$ ${CVSROOT}/CVSROOT/run-autoconf.pl
Attached is the run-autoconf perl script. I can think of a more general
approach (use an assoc array that is eval'd into the perl script to
maintain dependencies and add them to the "must be found" list) which I
could throw together if there's interest.
/r$
run-autoconf.pl
