Yipee,
Thanks Martin, it's been too long without huge controversial thread in
here. Foooooood fiiiiiiiiiiight!
>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> Did you know that Linux Mandrake 7.0's autoconf claims to be
Martin> version 2.14.1? (martin@wobble) /xemacs/build $ autoconf
Martin> --version Autoconf version 2.14.1
Grrr. I've even heard that even before I was member of the committee,
even before I ever ``publicly'' (i.e., here) talked of the pirate
Autoconf I was maintaining, an RPM packager took the copy he found in
my ftp dir, packaged it, and uploaded it to RedHat!
Now, there's a README-alpha which is rather explicit.
Martin> Did you know that this autoconf uses $SHELL instead of
Martin> ${CONFIG_SHELL-/bin/sh}?
Where?
Martin> This would fail in the most obvious way if the user's shell
Martin> was, say csh (untested).
Martin> My own SHELL is /bin/zsh,
I've always thought that peopling thinking and feeling like XEmacs
*must* run zsh. Seems like I was right :)
Martin> and this is sufficiently different from /bin/sh to cause it to
Martin> be unsuitable for a configure shell. You simply can't use
Martin> SHELL - that variable is reserved for the user's use.
Yes, you are right, but what use of SHELL are you refering to? CVS
Autoconf has
SHELL=${CONFIG_SHELL-/bin/sh}
which is harmless in your sense, and positive in our: we want to make
sure make is using the right shell.
Martin> 2.13 was a no-effort upgrade over 2.12. It doesn't look like
Martin> this will be true of 2.14.
We try to avoid this, but it was to be expected that people who partly
rewrite Autoconf have problems. I am surprised though.
Akim
