Bas Wijnen <wijnen@debian.org> writes:
> Autoconf is pretty stable,
This has not been the experience of many of us. I haven't had a lot of
trouble fixing things for newer releases of Autoconf, but I definitely
have seen issues. And the Autoconf 2.13 to 2.50 transition and all the
subsequent instability was not that long ago.
> so I suppose you're talking about automake. Because of its interface
> instability, you should never depend on "automake", but always on
> "automake1.10" (or whatever version you tested with).
Just FYI:
windlord:~> apt-cache policy automake1.10
automake1.10:
Installed: (none)
Candidate: (none)
Version table:
windlord:~> apt-cache policy automake
automake:
Installed: 1:1.10.1-2
Candidate: 1:1.10.1-2
Version table:
1:1.10.1-3 0
500 http://exodus.stanford.edu unstable/main Packages
*** 1:1.10.1-2 0
990 http://exodus.stanford.edu testing/main Packages
100 /var/lib/dpkg/status
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>