Bruno Haible <[email protected]> writes: > Hi Simon, > >> > This patch synchronizes the gettext *.m4 macros in Gnulib with those from >> > the newest GNU gettext release. *Except* that I'm not syncing po.m4, >> > because it may cause trouble when the newer po.m4 is combined with a >> > GNU gettext infrastructure from version < 0.24 >> >> I suppose making po.m4 support gettext < 0.24 is complicated? > > It would not be complicated. But the point of the changes in gettext 0.24 > was to get rid of hard-to-maintain cruft in po.m4 by moving the logic into > po/Makefile.in.in. Reintroducing this cruft for backward-compatibility > would be besides the point. > >> > (and such versions are still in common use, see >> > https://repology.org/project/gettext/versions ). >> >> I was going to suggest that since the problem only affects people >> building from git (right?) we could assume people have gettext >= 0.24 > > In a year or two, we will indeed be able assume this.
Both makes sense, thank you! >> but seeing that so many usual developer environments still doesn't ship >> modern gettext makes me think we can't do that. What is keeping Debian, >> Fedora etc on ancient gettext releases? > > At a distro level, in particular for distros that rely a lot on 'autoreconf', > they depend on Autoconf 2.73 which will fix sr #111272 and sr #111273. > Currently they are blocked by the fact that Autoconf 2.73 is not released yet. I see. /Simon
signature.asc
Description: PGP signature
