Basically, the latest gettext is 0.18, which is in Debian Sid
(unstable) but not yet in testing, stable, or any Ubuntu release. I
doubt it is in many other distros yet, either. It is, however, in
mingw-cross-env as well as MacPorts. It turns out that we all should
use the same gettext version to avoid build and runtime errors.
Contrary to what I thought, it is considered unsafe to use more than
So, we are going to have to move to gettext-0.18 in the fairly near
future. If we go ahead now, it would force some of us to install a
newer gettext outside of the usual package manager. If we wait, we
might delay being able to work on the cross-platform builds.
To the best of my knowledge, this doesn't affect end-users, just the
devs actually working on our programs.
I personally would favor going to 0.18, but I may be biased because
that is what is on my main home desktop.
---------- Forwarded message ----------
From: Bruno Haible <bruno@...>
Date: Sun, Jun 20, 2010 at 10:24 AM
Subject: Re: gettext 0.18 creating po/Makefile.in.in with wrong
To: David Bruce <davidstuartbruce@...>
Cc: bug-gnu-gettext <bug-gnu-gettext@...>, sanvila@...
David Bruce wrote:
> Can I safely leave this line out to allow the program to be built with
> either 0.17 or 0.18?
Not safely. You can do it, but the result would not be safe. Please read
the chapter "Integrating with CVS" at