Martin Buchholz <[EMAIL PROTECTED]> writes:
> Of course, it goes without saying here that a careful user will always
> rm -rf;tar xzf to create a new pristine tree to build and install. We
> all do that, right? Dirty trees are only for hacking. But we should
> try to do the Right Thing even when the user is careless.
Actually, I always do a:
mkdir -p build/`sys`
cd build/@sys && ../../configure # ...
cd build/@sys && make
`sys` and @sys being AFS parlance for an architecture-dependent directory.
Or rather, I usually do this on eight platforms simultaneously.
I really wish there were a good way of doing this that didn't require
autoconf to generate the makefiles in every subdirectory; I strongly
prefer the paradigm where there's one and only one makefile fragment
that's generated with configure information and all the other makefiles
just include it. But then, I like writing makefiles, and I like readable
makefiles. *wry grin*
Anyway, to drift back on-topic, I'll chime in and say that I agree with
the arguments in favor of turning off the cache by default. The only time
I've had it be useful is when configure is calling nested configure
scripts in subdirectories. (I'd turn it on for those packages, like
the web2c TeX distribution, that do that.)
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
