From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: gems.eclass review
Date: Sat, 14 Mar 2009 18:53:10 +0000 [thread overview]
Message-ID: <20090314185310.6bd33e6c@snowcone> (raw)
In-Reply-To: <1237053765.31719.4696.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
On Sat, 14 Mar 2009 21:02:45 +0300
Peter Volkov <pva@gentoo.org> wrote:
> I'm not sure here. Is it safe to export src_prepare function for
> EAPI=0,1?
Nope. You're only allowed to EXPORT_FUNCTIONS something that's a phase
function for your chosen EAPI.
(Incidentally, you're also only allowed to call EXPORT_FUNCTIONS once
per eclass. I seem to recall this being for historical reasons.)
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-14 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 16:47 [gentoo-dev] gems.eclass review Alex Legler
2009-03-07 3:03 ` [gentoo-dev] " Ryan Hill
2009-03-12 20:02 ` Alex Legler
2009-03-14 18:02 ` Peter Volkov
2009-03-14 18:53 ` Ciaran McCreesh [this message]
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=20090314185310.6bd33e6c@snowcone \
--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