%% [EMAIL PROTECTED] (Greg A. Woods) writes:
gaw> This nonsense of giving the user ultimate and complete control
gaw> over where each and every individual class of files, while at the
gaw> same time not learning and honouring platform specific policies
gaw> for the defaults (i.e. choosing defaults that might be suitable
gaw> only for one class of systems), is big nasty can of worms, each
gaw> of which has spiky spines and very sharp and fast-moving teeth!
No. This is exactly the right way to do it.
Autoconf should provide a well-defined set of directories, each with a
well-defined purpose/policy, and each with a default value based on one
global value (prefix) so they're simple to re-target en mass.
Then it should allow users who care about such things to modify each
individual value to suit their particular environment.
That's all it should do.
People who have to place everything "just so" can easily read the
INSTALL file and get the right options, or create a site config file, or
whatever. Autoconf should make things simple for the clueless user, and
make modification straightforward (e.g., no "magic guessing") for the
advanced user.
MO.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
