From: Pacho Ramos <pacho@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, "gnome@gentoo.org" <gnome@gentoo.org>
Subject: Re: [gentoo-dev] How to spread intltool fixes to all packages
Date: Mon, 17 Jun 2013 21:38:30 +0200 [thread overview]
Message-ID: <1371497910.22480.22.camel@localhost> (raw)
In-Reply-To: <201306170105.42908.vapier@gentoo.org>
El lun, 17-06-2013 a las 01:05 -0400, Mike Frysinger escribió:
[...]
> ELT-PATCHES is only used by elibtoolize which means it requires an explicit
> call to patch things
>
> you're basically talking about the same type of problem that
> https://bugs.gentoo.org/220040 tried to address. maybe we should update
> autotools.eclass to have a general patching mechanism since any EAPI based one
> is doomed to failure. and then we rebase elibtoolize to that.
> -mike
It looks a bit ambitious to me, but, if you think it is not so hard to
do, would be interesting :O
prev parent reply other threads:[~2013-06-17 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 9:55 [gentoo-dev] How to spread intltool fixes to all packages Pacho Ramos
2013-06-14 19:02 ` Pacho Ramos
2013-06-14 19:44 ` Alexis Ballier
2013-06-17 5:05 ` Mike Frysinger
2013-06-17 19:38 ` Pacho Ramos [this message]
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=1371497910.22480.22.camel@localhost \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gnome@gentoo.org \
--cc=vapier@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