[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf 3.0?
From: |
Bruce Korb |
Subject: |
Re: autoconf 3.0? |
Date: |
Fri, 13 Sep 2002 09:51:55 -0700 |
Alex Hornby wrote:
> Just to play devils advocate for a moment - wasn't a "system state" the
> whole problem with Imake?
>
> I remember using it, and the chances of a vendor's (think Sun, HP or
> Digital here) Imake settings being correct was approximately zero :)
It's true that different settings of PATH et al. will effect the outcome
of the probes. I would argue that someone with lots of different PATH
settings that they would want to install to would require lots of
different prefix directories that they would be installing into.
The worst case scenario would be having to install autoconf-setup
to a temporary directory (placed at the head of the PATH list),
then installing the package of interest. That's almost as bad as
fretting over shells that do not have functions. :-)
- Re: converting netkit to autoconf?, Akim Demaille, 2002/09/03
- Re: converting netkit to autoconf?, Bruce Korb, 2002/09/03
- Re: converting netkit to autoconf?, Paul Eggert, 2002/09/03
- Re: converting netkit to autoconf?, Earnie Boyd, 2002/09/03
- Re: converting netkit to autoconf?, Akim Demaille, 2002/09/13
- Re: converting netkit to autoconf?, Bruce Korb, 2002/09/13
- Re: converting netkit to autoconf?, Bernd Jendrissek, 2002/09/13
- Re: autoconf 3.0?, Bruce Korb, 2002/09/13
- Re: autoconf 3.0?, Alex Hornby, 2002/09/13
- Re: autoconf 3.0?,
Bruce Korb <=
- Re: converting netkit to autoconf?, Paul Eggert, 2002/09/13
- Re: converting netkit to autoconf?, Dan Kegel, 2002/09/13
- Re: converting netkit to autoconf?, Berend de Boer, 2002/09/15
- Re: converting netkit to autoconf?, Christopher Faylor, 2002/09/15