From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: FOO_subtract, the logical antidote to FOO_append.
Date: Wed, 16 May 2012 17:43:30 +0100 [thread overview]
Message-ID: <1337186611.1964.76.camel@phil-desktop> (raw)
In-Reply-To: <4FB3C2CC.7010204@windriver.com>
On Wed, 2012-05-16 at 10:07 -0500, Mark Hatle wrote:
> But the real problem we keep struggling with is .conf load order.. you try to
> set some nice value in local.conf, and some later configuration file adds to it,
> or simply overwrites it. He'd like a way to strip out things like that.
OVERRIDES .= ":local"
VAR_local = "I rule"
Or you could use the existing "_forcevariable" override although I have
a feeling that was intended for something else.
p.
next prev parent reply other threads:[~2012-05-16 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 19:01 RFC: FOO_subtract, the logical antidote to FOO_append Peter Seebach
2012-05-15 20:46 ` Manuel Bessler
2012-05-16 4:35 ` Saul Wold
2012-05-16 15:07 ` Mark Hatle
2012-05-16 16:23 ` Chris Larson
2012-05-16 16:43 ` Phil Blundell [this message]
2012-05-16 16:58 ` Peter Seebach
2012-05-18 4:18 ` Chris Larson
2012-05-18 6:25 ` Richard Purdie
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=1337186611.1964.76.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.