Re: Autoconf 2.50
Gordon Sadler <firstname.lastname@example.org> writes:
> Seeing autoconf 2.50 in unstable today prompts this message. My
> understanding is 2.50 will not work out-of-the-box with 2.13
It seems to me that there's in fact quite a bit of
backward-compatibility code in autoconf 2.50. If it turns out
that this isn't good enough for a lot of packages, then I'll
revert autoconf to 2.13 and put out a new autoconf-2.50 package.
"A computer is a state machine.
Threads are for people who cant [sic] program state machines."