public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] USE_EXPAND in profiles?
Date: Wed, 30 Mar 2016 21:07:46 -0700	[thread overview]
Message-ID: <56FCA292.80500@gentoo.org> (raw)
In-Reply-To: <1459347868.3538.32.camel@infinera.com>

On 03/30/2016 07:22 AM, Joakim Tjernlund wrote:
> On Thu, 2016-03-31 at 02:26 +1300, Kent Fredric wrote:
>> On 31 March 2016 at 01:49, Joakim Tjernlund
>> <Joakim.Tjernlund@infinera.com> wrote:
>>>
>>>
>>> I am missing something?
>>> Generally I think that everything possible to do under /etc/portage should be
>>> doable under a profile as well.
>>
>> So after you ignore my other stuff:  Profiles are part of the PMS
>> specification, so any changes that go in there have to be EAPI
>> scheduled and cried over for a bit, and probably GLEPs and stuff also.
>>
>> I guess portage could informally support it prior to any such
>> specification materialising, but it would have to be forbidden in the
>> main tree until such a specification was defined, or the portage tree
>> would become PMS in-compatible.
> 
> Yes, exactly! There is no need to use non PMS compatible features in
> the gentoo tree.

We hide extensions like this behind profile-formats settings in
metadata/layout.conf. Please file a feature request bug for this at
bugs.gentoo.org.
-- 
Thanks,
Zac


      reply	other threads:[~2016-03-31  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 12:49 [gentoo-portage-dev] USE_EXPAND in profiles? Joakim Tjernlund
2016-03-30 13:21 ` Kent Fredric
2016-03-30 13:22   ` Kent Fredric
2016-03-30 13:26 ` Kent Fredric
2016-03-30 14:22   ` Joakim Tjernlund
2016-03-31  4:07     ` Zac Medico [this message]

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=56FCA292.80500@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-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