public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: making USE_EXPANDed variables incremental
Date: Tue, 2 Jan 2007 20:21:45 +0000	[thread overview]
Message-ID: <20070102202145.62eb612d@snowdrop> (raw)
In-Reply-To: <20070102211419.5b5685f1@delenn.genone.homeip.net>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On Tue, 2 Jan 2007 21:14:19 +0100 Marius Mauch <genone@gentoo.org>
wrote:
| On Mon, 1 Jan 2007 21:12:47 +0000
| Stephen Bennett <spb@gentoo.org> wrote:
| > Following a discussion in #gentoo-portage earlier this evening, it
| > was suggested that I send out an RFC email for this. So, does anyone
| > object to requiring that any variable listed in USE_EXPAND be
| > treated as incremental, at least as far as profile inheritance is
| > concerned?
| 
| The main problem I see is that if it's becoming a real incremental
| (across all config layers) it would change behavior for users as
| they'd need to prefix their use-expanded vars with -* to retain their
| current config. But I guess that's why you added that final clause
| about profile scope.

You know, making users do that wouldn't necessarily be a bad thing... I
know that Paludis users like having the option of inheriting defaults
from the profile for expanded vars...

-- 
Ciaran McCreesh
Mail                : ciaranm at ciaranm.org
Web                 : http://ciaranm.org/
Paludis is faster   : http://ciaranm.org/show_post.pl?post_id=61


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-01-02 20:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 21:12 [gentoo-dev] RFC: making USE_EXPANDed variables incremental Stephen Bennett
2007-01-01 21:24 ` Donnie Berkholz
2007-01-01 21:44   ` Simon Stelling
2007-01-01 22:49   ` Stephen Bennett
2007-01-01 23:27     ` Donnie Berkholz
2007-01-01 23:32       ` Ciaran McCreesh
2007-01-01 23:47       ` Stephen Bennett
2007-01-02  1:24         ` Donnie Berkholz
2007-01-02  2:03           ` Stephen Bennett
2007-01-02  2:21             ` Donnie Berkholz
2007-01-02 20:14 ` Marius Mauch
2007-01-02 20:21   ` Ciaran McCreesh [this message]
2007-01-02 20:34     ` Marius Mauch
2007-01-02 21:02   ` Josh Saddler
2007-01-02 21:06   ` Stephen Bennett

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=20070102202145.62eb612d@snowdrop \
    --to=ciaranm@ciaranm.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