From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] elibtoolize/eautoreconf interactions and lazy eclasses/ebuilds
Date: Sun, 13 Nov 2011 23:28:00 +0530 [thread overview]
Message-ID: <CADqQcK6oBAKmCQ0Ok97X3_asjki+rFpA_Jd2RZkd6UK_-ygHLw@mail.gmail.com> (raw)
In-Reply-To: <4EC0024E.2030208@gentoo.org>
On Sun, Nov 13, 2011 at 11:15 PM, Samuli Suominen <ssuominen@gentoo.org> wrote:
> also a bug in those ebuilds then, since gnome2_src_prepare() should
> always be the last call/command in src_prepare()
>
It's slightly complicated. We don't always want gnome2_src_prepare to
be the last call in src_prepare for live ebuilds, and ebuilds where we
sed configure or Makefile.in directly to avoid an eautoreconf (it's
extremely slow on arm/mips etc).
It's very easy to not do the right thing. I think mike's change is a good thing.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2011-11-13 17:58 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 [this message]
2011-11-13 18:03 ` Mike Frysinger
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=CADqQcK6oBAKmCQ0Ok97X3_asjki+rFpA_Jd2RZkd6UK_-ygHLw@mail.gmail.com \
--to=nirbheek@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