From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] eapi files and profiles
Date: Fri, 23 Oct 2009 21:32:27 +0100 [thread overview]
Message-ID: <20091023213227.4baaf15b@snowcone> (raw)
In-Reply-To: <4AE21187.808@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Fri, 23 Oct 2009 23:26:47 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:
> Well technically you still shouldn't add EAPI 2 atoms to the child
> profiles without them being marked with the appropriate eapi file
> entry. Do all the levels of 10.0 profiles use EAPI 2 entries?
Down that way leads madness...
Mark any profile directory that itself uses EAPI 1 (there's nothing that
makes sense EAPI 2-wise for profiles) as EAPI 1. Leave any other
directory alone.
Doing it any other way requires far too much careful attention.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-23 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 8:24 [gentoo-dev] eapi files and profiles Samuli Suominen
2009-10-23 10:20 ` Ulrich Mueller
2009-10-23 20:26 ` Petteri Räty
2009-10-23 20:32 ` Ciaran McCreesh [this message]
2009-10-23 20:37 ` Ciaran McCreesh
2009-10-23 21:04 ` 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=20091023213227.4baaf15b@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