>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 19, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> Has anyone come up a reason why setting the ${prefix} and
>> ${exec_prefix} variables at the top of ./configure would be bad?
Alexandre> I think the point is to be able to tell whether it was the
Alexandre> user who chose /usr/local or if it's going to be used just
Alexandre> because it is the general default, so that a package
Alexandre> maintainer could override it. Of course, we have
Alexandre> AC_PREFIX_DEFAULT and AC_PREFIX_PROGRAM, that current rely
Alexandre> on that, but I'm sure we could use an auxiliary variable to
Alexandre> tell these macros whether the user specified --prefix or
Alexandre> not,
Yes, exactly! :) :) :) I should read the messages before answering.
Alexandre> but who knows what other macros out there rely upon these
Alexandre> variables being set to NONE?
Do you think some macros would behave differently if instead of NONE
we now have the real value?
Well, there is this in the doc:
| Here is a sample file `/usr/share/local/gnu/share/config.site'. The
| command `configure --prefix=/usr/share/local/gnu' would read this file
| (if `CONFIG_SITE' is not set to a different file).
|
| # config.site for configure
| #
| # Change some defaults.
| test "$prefix" = NONE && prefix=/usr/share/local/gnu
| test "$exec_prefix" = NONE && exec_prefix=/usr/local/gnu
| test "$sharedstatedir" = '${prefix}/com' && sharedstatedir=/var
| test "$localstatedir" = '${prefix}/var' && localstatedir=/var
| #
| # Give Autoconf 2.x generated configure scripts a shared default
| # cache file for feature test results, architecture-specific.
| if test "$cache_file" = ./config.cache; then
| cache_file="$prefix/var/config.cache"
| # A cache file is only valid for one C compiler.
| CC=gcc
| fi
but I'm not sure it would be that bad to make this change.
