Proposed Autoconf 2.50 path

[pfaffben@msu.edu (Ben Pfaff)]

A new package, autoconf2.13, has now been uploaded.  This package
provides a compatibility environment for Autoconf 2.13.  Packages
that really need this older version of Autoconf can use it by
replacing `autoconf' invocations by `autoconf2.13', and so on.

I propose to file a bug report on every package that
Build-Depends: on autoconf that does not compile properly with
Autoconf 2.50, saying that it either be fixed or modified to use
autoconf2.13 instead.

Question - how can I determine which packages do not compile
properly with Autoconf 2.50?  Is there a machine I can use to do
this?  (I don't have good-enough network connectivity to do it
here.)  Is the alternative of simply filing a bug on *every*
package that Build-Depends: on autoconf acceptable?

-- 
"Implementation details are beyond the scope of the Java virtual
 machine specification.  One should not assume that every virtual
 machine implementation contains a giant squid."
--"Mr. Bunny's Big Cup o' Java"