public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT* and USE_EXPAND additions
Date: Fri, 15 Apr 2005 23:20:43 +0900	[thread overview]
Message-ID: <200504152320.43912.jstubbs@gentoo.org> (raw)
In-Reply-To: <20050415141814.5438cac1@snowdrop>

On Friday 15 April 2005 22:18, Ciaran McCreesh wrote:
> On Fri, 15 Apr 2005 22:14:59 +0900 Jason Stubbs <jstubbs@gentoo.org>
>
> wrote:
> | If this actually scared anybody (that received it), my apologies. I
> | was  confused about bugs. Fixing the flat profiles will be problem
                                                         ^not^a^
> | either. The bug  is that 2.0.50 will die if two profiles in a cascade
> | define the same  variable.
>
> Which should be fine, because no-one is even going to *think* about
> wanting sub-profile-specific USE_EXPAND. Right?

USE_EXPAND is not an incremental.

The only other settings that directly relate to ebuilds and currently live in 
make.globals are CONFIG_PROTECT and CONFIG_PROTECT_MASK. These should also be 
moved into the tree. Any objections?

Regards,
Jason Stubbs
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-04-15 14:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 11:48 [gentoo-dev] USE_EXPAND additions Jason Stubbs
2005-04-13 18:07 ` Donnie Berkholz
2005-04-13 18:57 ` Stephen Bennett
2005-04-13 18:56   ` Kito
2005-04-14 14:26 ` Jason Stubbs
2005-04-15 13:14   ` Jason Stubbs
2005-04-15 13:18     ` Ciaran McCreesh
2005-04-15 14:20       ` Jason Stubbs [this message]
2005-04-15 14:26         ` [gentoo-dev] CONFIG_PROTECT* and " Ciaran McCreesh
2005-04-15 18:53     ` [gentoo-dev] " Paul de Vrieze
2005-04-16  0:56       ` Brian Harring
2005-04-16  1:08       ` Jason Stubbs

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=200504152320.43912.jstubbs@gentoo.org \
    --to=jstubbs@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