public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] eapi files and profiles
Date: Fri, 23 Oct 2009 11:24:27 +0300	[thread overview]
Message-ID: <4AE1683B.7090106@gentoo.org> (raw)

So I was told Council needs to approve inheritance of eapi files from
parent profiles?

I'm not sure why, because we shouldn't have any files in default/linux/
which was decided long ago when the new profiles was introduced...

gentoo-x86/profiles/default/linux $ find ./ -name eapi | wc -l
63

That's 63 duplicated files. We should only have one releases/10.0/eapi
file, and others wouldn't be required as it would cover all the 10.0
profiles.

See, http://bugs.gentoo.org/288320

Can we get a decision on this soon, so we can drop the duplication for
10.1 (or whatever the name for next profile set will be called) ?



             reply	other threads:[~2009-10-23  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  8:24 Samuli Suominen [this message]
2009-10-23 10:20 ` [gentoo-dev] eapi files and profiles Ulrich Mueller
2009-10-23 20:26   ` Petteri Räty
2009-10-23 20:32     ` Ciaran McCreesh
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=4AE1683B.7090106@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --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