From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI-2 and src_configure in eclasses
Date: Sun, 5 Oct 2008 15:24:20 +0100 [thread overview]
Message-ID: <20081005152420.1d1e3256@googlemail.com> (raw)
In-Reply-To: <20081005161546.31446f38@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Sun, 5 Oct 2008 16:15:46 +0200
Alexis Ballier <aballier@gentoo.org> wrote:
> An eapi.eclass with such functions and lists of eapi & features
> maintained there could help though.
The problem is, 'features' change between EAPIs. For example, all three
EAPIs have src_compile, but it does different things for all three. One
can't assume that a feature working for current EAPIs will carry on
working for future EAPIs, and even if it does there can be other
interactions that break.
> An EXPORT_FUNCTIONS ignoring any function its doesn't know for its
> eapi would help too.
An EXPORT_FUNCTIONS ignoring incorrect usage makes one less place
checking for eclass screwups...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-05 14:24 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 [this message]
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 ` [gentoo-dev] " Ulrich Mueller
2008-10-05 15:41 ` 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=20081005152420.1d1e3256@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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