Re: Autoconf release

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Paul Eggert on 6/19/2006 12:33 AM:
> Ralf Wildenhues <address@hidden> writes:
> 
>> I am considering postponing 2.60 for a couple of days because of some
>> pending issues, allowing for a comment period for some posted patches,
>> and a bit of time to think about the m4wrap issue.
> 
> Fine with me.
> 
> One possibility for m4wrap is to do nothing until after 2.60 is out.
> I.e., if m4 2.0 isn't expected to be out soon, we can fix m4wrap
> issues in Autoconf 2.61.

I'll put it this way.  If 2.60 adds an m4wrap workaround, then m4 2.0
might come out before autoconf 2.61.  But if 2.60 does not add an m4wrap
workaround, then m4 development will have to wait for yet another autoconf
release.  One of my criteria for a successful m4 2.0 release is that it
must be a drop-in replacement on top of 1.4.x from autoconf's perspective
(and while we aren't there yet, it may be possible to get there in the
next few months).

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFElpjT84KuGfSFAYARAhWzAJ9EiLkMj6c/xyeWNamB9TdWQc3O6QCaAnal
bWZ4uv6jIDLHPetNU+FkKCU=
=eRQw
-----END PGP SIGNATURE-----