From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 09-10-2012
Date: Thu, 04 Oct 2012 20:32:41 +0200 [thread overview]
Message-ID: <1349375561.2200.57.camel@belkin4> (raw)
In-Reply-To: <1349284689.2200.50.camel@belkin4>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
El mié, 03-10-2012 a las 19:18 +0200, Pacho Ramos escribió:
> El mar, 02-10-2012 a las 13:30 +0200, Fabian Groffen escribió:
> > Pacho,
> >
> > On 25-09-2012 21:32:50 +0200, Pacho Ramos wrote:
> > > This is from:
> > > http://www.gossamer-threads.com/lists/gentoo/dev/260662
> > >
> > > But corrected to remember preferred usage of in_iuse from eutils.eclass
> > > as remembered by mgorny in that thread:
> >
> > I've considered your point, but concluded that at this moment, the
> > Council basically has nothing to do here. It seems obvious that it
> > needs something to be defined in a next EAPI, but the Council is not the
> > body to invent that.
> > Please discuss with involved people (Portage devs?) and prepare a patch
> > to PMS that can be used as feature for the next EAPI. Brian's
> > IUSE_FLATTENED might be a simple and good solution for that.
> >
> > Best,
> > Fabian
> >
>
> And what about current usage in the tree with current eapis? Regarding
> IUSE_FLATTENED I have no problem with it, but will need to talk with
> portage team also as they have the current implementation
And then, I think council should clarify what to do with current usages
in the tree with eapi0-4
Thanks
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-04 21:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 9:24 [gentoo-project] Call for agenda items -- Council meeting 09-10-2012 Fabian Groffen
2012-09-25 9:59 ` Ulrich Mueller
2012-09-27 6:19 ` Ulrich Mueller
2012-09-27 22:13 ` Brian Harring
2012-09-28 0:14 ` Ulrich Mueller
2012-09-28 12:12 ` Brian Harring
2012-10-03 5:04 ` Donnie Berkholz
2012-10-03 6:44 ` Ulrich Mueller
2012-10-03 6:56 ` Matt Turner
2012-10-03 8:31 ` Ulrich Mueller
2012-09-29 15:51 ` Ciaran McCreesh
2012-09-29 16:04 ` Ulrich Mueller
2012-09-29 16:10 ` Ciaran McCreesh
2012-09-25 19:32 ` Pacho Ramos
2012-10-02 11:30 ` Fabian Groffen
2012-10-03 17:18 ` Pacho Ramos
2012-10-04 18:32 ` Pacho Ramos [this message]
2012-10-05 6:28 ` Fabian Groffen
2012-10-05 6:41 ` Pacho Ramos
2012-10-05 6:43 ` Patrick Lauer
2012-10-05 8:46 ` Ulrich Mueller
2012-10-05 10:31 ` Rich Freeman
2012-10-05 14:51 ` Jeff Horelick
2012-10-05 17:35 ` Pacho Ramos
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=1349375561.2200.57.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-project@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