Re: --localdir backwards compatibility

[Niels Möller]

Akim Demaille <address@hidden> writes:

> Please, drop 2.13, as it is too buggy, and trying to maintain
> compatibility with it is the worse that could happen to your scripts.

Well, there's a lot of nifty stuff in the latest autoconf that I like,
but there are also some more controversial things (like the
perl/autom4te stuff, not using config.cache by default, and it seems
to be an order of magnitude slower than autoconf-2.13). I use and
require the latest autoconf for my own projects, but I don't think
autoconf-2.13 is going to disappear soon.

So for me, the problem is that I want to have 2.57 installed on my
machine, and still be able to do development on projects, like pike,
that prefer to use autoconf-2.13 or autoconf-2.52. And that *works*,
I've noticed *no* problems with, except for the annoying renaming of
--localdir.

I'm actually considering getting the latest pre-autom4te version of
autoconf (2.52?), and see if I can put it together with the m4 files
of the latest autoconf release. ;-)

Regards,
/Niels