Re: Autoconf 2.50
On Thu, 24 May 2001, Junichi Uekawa wrote:
> I would suggest reverting "autoconf" to be the compatibility
> version, and applications which work with autoconf-2.50
> can build-depend upon it, after being verified as such.
If it's done "just like that", it will take years before we start using
anything other than 2.13. This is not acceptable.
I'd suggest that a deadline (e.g. woody is released) is set by the autoconf
maintainer, and after that deadline is past, he would unmercifuly bump up
the 'default' autoconf up to whatever is the newest stable version. If a
package breaks then, tough luck - it gets a serious bug.
Meanwhile, giving us a autoconf-2.5 package that provides: autoconf and
reverting the autoconf package to 2.13 would avoid the possibility of
delaying woody, and still allow packages to be fixed for 2.5x in a steady
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot