>>>>> "Erez" == Erez Zadok <[EMAIL PROTECTED]> writes:
Erez> That's good news, Akim.
Oh yes it is! :)
Erez> Now, do you have a schedule for when a feature freeze will
Erez> happen, and when this autoconf will work with automake 1.4a?
We've not talked about this yet, but personally I'm not satisfied
yet. At some point in the past it would have been OK to release a
2.15 as is, but since then we took the decision to clean up the code,
and to promote better coding styles. Therefore, although the next
Autoconf will be backward compatible, we do expect people to follow
the new standards. It should not happen several times, hence 2.15
should provide a base layer that satisfies everybody.
Today, it is not the case.
And, as you noted, the integration with Automake is still to be done.
But I'm optimistic. It is good that Tom doesn't jump on Autoconf as
is today, because Autoconf is trying to reach him. IMHO, doing
efforts in Automake today is wasting time.
Erez> After these two happen, I'd like to test autoconf on all of my
Erez> platforms. I do it in two ways: (1) run make test, and (2) use
Erez> it in my am-utils package.
I understand you want to delay (2), but since I believe you have
access to a great many architectures, since I think you have scripts
that performs the tests in batch, I would really feel better if you
could try it a least once early. Way before the code freeze. Some
people already *rely* on CVS Autoconf.
Erez> It's also easier for me to do the two things at once, esp. since
Erez> I have to login to dozens of machines scattered around the
Erez> Internet.
Well, I am certainly not asking you to `work', but if you have
something automated which costs nothing to run, included if it is on a
small set of machines, it'd be great.
Thanks!
Akim
