From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: DEFINED_PHASES magic metadata variable
Date: Fri, 5 Dec 2008 15:01:56 +0000 [thread overview]
Message-ID: <20081205150156.644974b0@snowcone> (raw)
In-Reply-To: <20081127194359.05327003@snowmobile>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Thu, 27 Nov 2008 19:43:59 +0000
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> The DEFINED_PHASES variable will contain a space separated arbitrarily
> ordered list of phase names. A phase name is listed in DEFINED_PHASES
> if and only if the ebuild or an eclass used by that ebuild provides an
> implementation of that phase's phase function.
This needs "or if the ebuild or an eclass used by that ebuild provides
a pre_ or post_ Portage hook for that phase", unless the Java people
are prepared to nuke their horrid icky java-pkg.eclass hack that works
around a now-fixed Portage bug.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-05 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 19:43 [gentoo-dev] RFC: DEFINED_PHASES magic metadata variable Ciaran McCreesh
2008-12-05 15:01 ` Ciaran McCreesh [this message]
2008-12-06 15:40 ` [gentoo-dev] " Petteri Räty
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=20081205150156.644974b0@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