autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoconf auxdir


From: Ralf Corsepius
Subject: Re: autoconf auxdir
Date: Thu, 12 Apr 2001 15:51:20 +0200

Akim Demaille wrote:
> 
> >>>>> "Earnie" == Earnie Boyd <address@hidden> writes:
> 
> Earnie> Alexandre Oliva wrote:
> >>
> >> On Apr 12, 2001, Akim Demaille <address@hidden> wrote:
> >>
> >> > aux means nothing and is not portable.  auxdir is puke puke puke
> >>
> >> Agreed.  I still like AC_CONFIG_SUPDIR better than
> >> AC_CONFIG_CONFIGDIR or AC_CONFIG_CFGDIR.
> >>
> 
> Earnie> I do too.  Akim has already given examples of where the
> Earnie> auxiliary directory is used for more than just
> Earnie> autoconfiguration so IMHO promoting config/ isn't a fair use
> Earnie> of the function.  If you want to promote
> Earnie> $ac_config_supdir/config/ as the directory of choice for
> Earnie> autoconfiguration files then that is fair use and I would
> Earnie> promote that use.
> 
> Hm, I think I'm lost, or we don't talk about the same thing.
Hmm, just a guess: $ac_config_*dir vs. config/?

>  I'd like to promote config/ as the common AC_CONFIG_AUX_DIR,
I dislike this idea: Using config is as error-prone as is using aux,
as is promoting any name, because arbitrary packages already might
use any arbitrary name for any arbitrary purpose.

Leave the user the freedom to use what he likes, the name of the
macro actually doesn't matter.

Ralf

Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]