From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "gnome@gentoo.org" <gnome@gentoo.org>
Subject: [gentoo-dev] How to spread intltool fixes to all packages
Date: Tue, 11 Jun 2013 11:55:14 +0200 [thread overview]
Message-ID: <1370944514.4583.28.camel@localhost> (raw)
Hello
Because of:
https://bugs.gentoo.org/show_bug.cgi?id=432848
We discovered an old bug affecting intltool that causes prefix of
localedir to be always hardcoded to the same location instead of
respecting configure flags.
The patch is fixed by intltool upstream in their master branch but still
no new version was released including it. Anyway, we now have
dev-util/intltool-0.50.2-r1 with the bug fixed.
The problem of this issue (and most involving intltool) is that we need
to run:
intltoolize --copy --automake --force
(it doesn't seem to trigger maintainer mode in all ebuilds I have tried,
then, doesn't look to require eautoreconf to be run)
for all packages to get new and fixed ${S}/po/Makefile.in.in copied to
the sources, otherwise bundled file is used and, then, the one unfixed.
As it's unreliable to ping all upstreams involving intltool (they are a
ton) and this kind of problem will likely re-appear again in the future
(since the Makefile.in.in will be fixed in intltool upstream tarball but
will take a lot of time to reach all affected packages) we were
considering to run above command always at eclass level -> that way we
would stop using bundled ${S}/po/Makefile.in.in and, then, we would
always use the one provided by our intltool package (that should get
fixed and updated more often).
Other possible solution would be to use ELT-PATCHES to achieve that, but
I am still unsure about how would it work.
What are your thoughts?
next reply other threads:[~2013-06-11 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 9:55 Pacho Ramos [this message]
2013-06-14 19:02 ` [gentoo-dev] How to spread intltool fixes to all packages Pacho Ramos
2013-06-14 19:44 ` Alexis Ballier
2013-06-17 5:05 ` Mike Frysinger
2013-06-17 19:38 ` Pacho Ramos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1370944514.4583.28.camel@localhost \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gnome@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox