On Wed, Sep 13, 2006 at 08:39:49PM +0200, Denis Barbier wrote: > On Wed, Sep 13, 2006 at 11:57:42AM +0200, Santiago Vila wrote: > > On Thu, 7 Sep 2006, Steve Langasek wrote:
> > > On Wed, Sep 06, 2006 at 11:33:17AM +0000, Martin Michlmayr wrote: > > > > # Rebootstrap the package > > > > aclocal -I macros > > > > aclocal: macro `AM_PROG_MKDIR_P' required but not defined > > > > aclocal: macro `AM_PROG_MKDIR_P' required but not defined > > > So in addition to the gettext pseudobug (#385235), we seem to have an > > > incompatibility between the latest gettext and automake 1.4/1.7. These > > > versions are still in active use, which makes it impractical to include a > > > gettext in etch that doesn't support them. > > Simple question: Is this the kind of bug that may be forwarded upstream > > and fixed? > No, these bugs are not caused by gettext itself, but by bad practices. > Let's look at all different cases: > 1. aclocal is not called during package build: > aclocal.m4 and po/Makefile.in.in come from upstream and are > compatible. > 2. aclocal is called during package build: > 2.a. gettext.m4 is found in a local copy, usually under m4/ > There is no problem, m4/gettext.m4 and po/Makefile.in.in come > from upstream and are compatible > 2.b. gettext.m4 is found in /usr/share/aclocal/ > Here gettext.m4 may be incompatible with po/Makefile.in.in > The only problem is with 2.b. In this case, developers should call > autopoint before aclocal. Bruno Haible provided autopoint for this > exact purpose. It can regenerate m4/gettext.m4 and > po/Makefile.in.in for any previous version of gettext, this tool > is really great. Since autopoint 0.11.3, one can for instance add > AM_GNU_GETTEXT_VERSION([0.12.1]) > just after AM_GNU_GETTEXT in configure.ac to request files from > gettext 0.12.1. This is useful with packages which depend on > automake 1.4, one can use more recent versions; ideally we should > try to reproduce the exact same version as upstream to avoid > problems. And this fixes the problem that the current version of gettext.m4 depends on AM_PROG_MKDIR_P, a macro introduced in automake 1.8? In any case, I agree that there is no reason for a separate gettext-0.14 package, but I don't see how autopoint solves the problem of the undefined macro which has to do with compatibility of older versions of *automake*, not with older versions of *gettext*; in which case it would still be nice to have a solution for making a gettext.m4 available that's compatible with the automake-1.4 and automake-1.7 we still ship. (But indeed, no longer RC if all the packages build-depending on gettext have been fixed.) Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
