Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] bitbake.conf: make OVERRIDES match what people expect
Date: Tue, 24 May 2011 16:24:56 +0100	[thread overview]
Message-ID: <1306250696.3424.937.camel@rex> (raw)
In-Reply-To: <1306250123.2525.205.camel@phil-desktop>

On Tue, 2011-05-24 at 16:15 +0100, Phil Blundell wrote:
> On Tue, 2011-05-24 at 16:07 +0100, Richard Purdie wrote:
> > It was added to poky with the intent of doing what "_local" would have
> > done before it was broken.
> > 
> > I think its a little safer than using "local" as the override keyword,
> > I'm open to opinion on whether it should be kept but it probably has
> > uses.
> 
> Ah, I see.  I must admit that I wouldn't have guessed that from the
> name.
> 
> Maybe we should just delete both _local and _forcevariable from the
> default OVERRIDES on the basis that nothing in the metadata (as
> distributed) uses either of them.  Anybody who wants to make use of them
> from local.conf or whereever can always add them back to OVERRIDES in
> the same place.

I'm ok with that, it can also be done by the distro...

Cheers,

Richard




  reply	other threads:[~2011-05-24 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 14:04 [RFC][PATCH] bitbake.conf: make OVERRIDES match what people expect Koen Kooi
2011-05-24 14:16 ` Richard Purdie
2011-05-24 14:58   ` Khem Raj
2011-05-24 15:03   ` Phil Blundell
2011-05-24 15:07     ` Richard Purdie
2011-05-24 15:15       ` Phil Blundell
2011-05-24 15:24         ` Richard Purdie [this message]
2011-05-24 19:54           ` Jeremy Puhlman
2011-05-26 15:18 ` Koen Kooi
2011-05-26 23:37   ` Richard Purdie
2011-05-30  7:33 ` 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=1306250696.3424.937.camel@rex \
    --to=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox