From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI-2 and src_configure in eclasses
Date: Sun, 5 Oct 2008 17:38:11 +0200 [thread overview]
Message-ID: <18664.57187.605226.301832@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <20081005161546.31446f38@gentoo.org>
>>>>> On Sun, 5 Oct 2008, Alexis Ballier wrote:
> Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
>> Export it if and only if EAPI is 2.
> By the way, do we really want to special case eapi-2 in every eclass ?
> That's lot of code duplication and will get even worse when we'll reach
> eapi-42. That would have been cool to have a pm function that tells
> "has my eapi foo support" but that sort of bites its tail that way.
Hm, what about:
[ "$(type -t src_configure)" == function ] && EXPORT_FUNCTIONS src_configure
Or is this too fragile or trying to be too clever?
Ulrich
next prev parent reply other threads:[~2008-10-05 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 13:36 [gentoo-dev] EAPI-2 and src_configure in eclasses Ulrich Mueller
2008-10-05 14:07 ` Ciaran McCreesh
2008-10-05 14:15 ` Alexis Ballier
2008-10-05 14:24 ` Ciaran McCreesh
2008-10-05 15:07 ` Alexis Ballier
2008-10-05 15:17 ` Ciaran McCreesh
2008-10-05 17:11 ` Zac Medico
2008-10-05 20:03 ` Ciaran McCreesh
2008-10-05 20:24 ` Zac Medico
2008-10-07 15:49 ` [gentoo-dev] " Steve Long
2008-10-09 8:26 ` Alexis Ballier
2008-10-10 7:17 ` Alec Warner
2008-10-10 12:41 ` Duncan
2008-10-10 16:06 ` Alec Warner
2008-10-05 15:38 ` Ulrich Mueller [this message]
2008-10-05 15:41 ` [gentoo-dev] " Ciaran McCreesh
2008-10-07 16:07 ` [gentoo-dev] " Steve Long
2008-10-07 16:33 ` Ciaran McCreesh
2008-10-08 18:48 ` [gentoo-dev] [project] " Steve Long
2008-10-08 3:21 ` [gentoo-dev] " Brian Harring
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=18664.57187.605226.301832@a1ihome1.kph.uni-mainz.de \
--to=ulm@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