From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] elibtoolize/eautoreconf interactions and lazy eclasses/ebuilds
Date: Sun, 13 Nov 2011 13:03:17 -0500 [thread overview]
Message-ID: <201111131303.17911.vapier@gentoo.org> (raw)
In-Reply-To: <4EC0024E.2030208@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 957 bytes --]
On Sunday 13 November 2011 12:45:50 Samuli Suominen wrote:
> On 11/13/2011 07:37 PM, Mike Frysinger wrote:
> > but i've hit this since with cross-compiling Linux targets:
> > - pygobject ebuild inherits gnome2 eclass
> > - pygobject's src_prepare first calls gnome2_src_prepare
> > - gnome2_src_prepare always calls elibtoolize (which normally is good)
> > - pygobject's src_prepare applies patches and then calls eautoreconf
> > - eautoreconf regens all files that where patched earlier
> > - eautoreconf's call to elibtoolize is skipped
> > - builds fail which need those elibtoolize patches
>
> also a bug in those ebuilds then, since gnome2_src_prepare() should
> always be the last call/command in src_prepare()
yes, but the current state is that people don't notice and things silently
break. i'm turning the situation into a QA warning so bug reports get
filed/fixed, and things continue to work in the mean time.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-13 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 17:37 [gentoo-dev] elibtoolize/eautoreconf interactions and lazy eclasses/ebuilds Mike Frysinger
2011-11-13 17:45 ` Samuli Suominen
2011-11-13 17:58 ` Nirbheek Chauhan
2011-11-13 18:03 ` Mike Frysinger [this message]
2011-11-14 17:09 ` Mike Frysinger
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=201111131303.17911.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.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