Re: Autoconf should not require to be in the path

[Ralf Corsepius]

Am Don, 2002-02-14 um 01.12 schrieb Paul Eggert:
> > From: Akim Demaille <address@hidden>
> > Date: Wed, 13 Feb 2002 13:38:33 +0100
> > 
> > Hard coding positions of executables seems like a bad idea to me :(
> > 
> > Paul?
> 
> I tend to agree; it causes problems when people move executables.
Though I agree to this in general, this consideration does not apply to
autom4te:

autom4te already contains a hard-coded path to its perl-modules:

>From autom4te:
[..]
BEGIN
{
  my $datadir = ($ENV{'autom4te_perllibdir'} ||
'/opt/dev/share/autoconf');
  unshift @INC, "$datadir";
}
[..]

=> autoconf already is "non-moveable/non-relocatible".
=> hard-coding the path into "autoconf" instead of "autom4te" would not
make the autoconf more non-relocatible than it already is.

Ralf