[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Autoconf should not require to be in the path
From: |
Tom Tromey |
Subject: |
Re: Autoconf should not require to be in the path |
Date: |
17 Feb 2002 11:52:48 -0700 |
>>>>> "Paul" == Paul Eggert <address@hidden> writes:
>> Would it at least make sense that if autoconf is called
>> /mumble/autoconf
>> then
>> /mumble/autom4te
>> is called?
Paul> That would violate the GNU coding standards, which say:
Paul> Please don't make the behavior of a utility depend on the name used
Paul> to invoke it. It is useful sometimes to make a link to a utility
Paul> with a different name, and that should not change what it does.
That's true but it is also true that running /foo/bar/autoconf and
having it fail is less than friendly. For one thing it makes it
harder for me to have multiple copies around at once.
What if autoconf had the path to autom4te compiled in?
That would suffice for my purposes.
Tom