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:37:53 +0100 [thread overview]
Message-ID: <20091023213753.5f90a8c5@snowcone> (raw)
In-Reply-To: <4AE1683B.7090106@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
On Fri, 23 Oct 2009 11:24:27 +0300
Samuli Suominen <ssuominen@gentoo.org> wrote:
> So I was told Council needs to approve inheritance of eapi files from
> parent profiles?
As a full explanation of why this idea sucks, since some people have
asked:
You need to decide which way eapi inherits go. Are you saying that any
profile directory with a parent using EAPI X is itself EAPI X? If so,
the implications are:
* that we can't change the format of the parent file ever (and we have
done so in the past)
* that it gets a lot harder to remove certain syntax in newer EAPIs.
For example, say we want to replace =...* with ranged dependencies in
EAPI 4. Then you can't change a profile directory to use EAPI 4
without checking that everything that uses that directory doesn't
make use of =...*.
Or are you saying that the package manager should use the eapi it picks
up for any parents it follows? If so, the implications are:
* that removing =...* in EAPI 4 (for example) becomes impossible,
because it would be impossible to use that syntax in high level
profiles that might be inherited by profiles using EAPI 4.
Either way, putting eapi files in any directory that itself
specifically needs it is a heck of a lot easier for everyone.
On top of that, if you do change it, there's the usual year wait before
you can use it, since current package managers don't inherit eapis.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-23 20:38 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
2009-10-23 20:37 ` Ciaran McCreesh [this message]
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=20091023213753.5f90a8c5@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