Ben Collins-Sussman <sussman@collab.net> writes:
> 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? :-)
Now, let's be fair :-). The system is a lot better than the norm in
many respects... Even in this respect, if you consider the usual
alternative: many systems require developers to remember to update a
statically maintained list whenever they add a new C file. Our system
generates that list automatically, you just have to remember to run
the generator now and then. Both ways are error prone, but at least
our way you don't have to go crawling over the logs to figure out how
to update the list when something goes wrong.
Still, it would be nice if we could somehow notice added files and set
a flag, so the programmer gets a nice error instead of an arbitrary
"build failed" error. But the only way I can think of right now is
via generic client side hooks
*** CRINGE ***
and we just shouldn't go there, since that essentially requires a
built-in extension language.
Is there some other solution? Greg, thoughts?
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 24 18:28:48 2002