Bruno Haible via Gnulib discussion list <[email protected]> writes:
> Hi,
>
> We assume that a GNU package maintainer who uses Gnulib uses the newest
> versions of the build tools (Autoconf, Automake, etc.).
>
> When gettext 1.0 was released, I refrained from upgrading po.m4 in
> gnulib, because there is some known interoperation problem between
> the recent gettext versions and Autoconf 2.72. [1]
>
> But this situation causes trouble in the release process [2].
>
> Now that Autoconf 2.73 has been released, it should be possible for every
> developer to installed Autoconf 2.73 and gettext 1.0 from source, right?
>
> Please speak up if you disagree.
Usually I use whatever is packaged in the latest Fedora release:
$ gettext --version | head -n 1
gettext (GNU gettext-runtime) 0.25.1
$ /bin/autoconf --version | head -n 1
autoconf (GNU Autoconf) 2.72
But building them from source is fine with me. Given that those versions
are very new, it might be a good idea to check them and give a helpful
error if they are too old. I doubt the build errors caused by having old
versions would be very helpful, but I haven't looked.
Collin
