Paul Eggert writes: > The code currently assumes Autoconf 2.60 but could be backported easily
I think it's important to leave people a choice. Autoconf 2.60 will have different bugs than autoconf-2.59, which had different bugs than 2.57. I think it's fine to now drop support for autoconf-2.57 and -2.58. But forcing people to using a specific release is creating constraints that are weird to satisfy. For example, if someone wants to keep using po/Makefile.in.in from gettext-0.14.x, at first sight he cannot upgrade to autoconf-2.60 without getting warnings. (OK, he can if he uses AC_DATAROOTDIR_CHECKED, but maybe he then falls into some bugs we don't know about yet.) A few years ago, the required versions of glibc and gcc were tied; likewise the versions of autoconf and automake were constrained. These were major annoyances. And with gnulib, we don't want to annoy people. Bruno
