gen-make.py

Greg, I know I've asked this before, but I don't remember your
rationale.

Our build system, gen-make.py, is a bit non-standard. Newbies are
constantly bitten every time a new C file appears in our tree.

The typical build-system maintains a list of C files in Makefile.in.
People know and expect this. If Makefile.in changes, then everyone
understands that ./configure needs to regenerate the Makefile. Most
people have developed a reflex of "cvs up; ./configure; make".

What's "nonstandard" about our system is the fact that you have to
re-run *autogen.sh* (or gen-make.py) when new C files are added.
Nobody suspects that. It's quite weird. It bites people constantly.
If I had a nickel for every dev-list post...!

Please remind me why our system is so much better than the norm? :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 24 16:37:01 2002