From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New eclass for x11 packages
Date: Mon, 22 Feb 2010 16:50:56 +0100 [thread overview]
Message-ID: <4B82A7E0.4070501@gentoo.org> (raw)
In-Reply-To: <4B8292C8.90902@gentoo.org>
Tomáš Chvátal wrote:
> Dne 22.2.2010 11:50, Michael Haubenwallner napsal(a):
>> PS: Just a suggestion what an ebuild could do in this case:
>> src_prepare() {
>> xorg-2_src_prepare --force-eautoreconf
>> }
> SNAPSHOT="yes" xorg-2_src_prepare
>
> ^ this does not fit your needs? It does exactly what you want :]
Uhh, this doesn't look like the "clean" way and depends on
exakt knowledge how xorg-2_src_prepare works - shouldn't
eclasses provide something like an "intuitive API" to some
degree, especially if they are "new"?
However - I'll continue looking into the eclass impl details...
/haubi/
--
Michael Haubenwallner
Gentoo on a different level
next prev parent reply other threads:[~2010-02-22 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 22:33 [gentoo-dev] [RFC] New eclass for x11 packages Tomáš Chvátal
2010-02-18 22:39 ` Jeremy Olexa
2010-02-18 23:04 ` Tomáš Chvátal
2010-02-18 23:06 ` Tomáš Chvátal
2010-02-18 23:11 ` David Leverton
2010-02-18 23:16 ` Tomáš Chvátal
2010-02-18 23:20 ` Tomáš Chvátal
2010-02-18 23:22 ` David Leverton
2010-02-19 1:22 ` [gentoo-dev] " Ryan Hill
2010-02-24 20:54 ` Tomáš Chvátal
2010-02-22 10:50 ` [gentoo-dev] " Michael Haubenwallner
2010-02-22 14:20 ` Tomáš Chvátal
2010-02-22 15:50 ` Michael Haubenwallner [this message]
2010-02-22 15:57 ` Tomáš Chvátal
2010-02-27 12:18 ` Tomáš Chvátal
2010-03-01 8:58 ` Michael Haubenwallner
2010-03-01 10:38 ` Samuli Suominen
2010-03-07 10:52 ` Rémi Cardona
2010-03-10 14:13 ` Tomáš Chvátal
2010-03-10 19:40 ` Dawid Węgliński
2010-03-10 19:42 ` Tomáš Chvátal
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=4B82A7E0.4070501@gentoo.org \
--to=haubi@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