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:07:55 +0100	[thread overview]
Message-ID: <1306249675.3424.936.camel@rex> (raw)
In-Reply-To: <1306249385.2525.203.camel@phil-desktop>

On Tue, 2011-05-24 at 16:03 +0100, Phil Blundell wrote:
> On Tue, 2011-05-24 at 15:16 +0100, Richard Purdie wrote:
> > I've been thinking through the different use cases and briefly talked
> > with Koen offlist about this. I think the revised order makes sense with
> > what users would expect and am happy to remove local and fail-fast as
> > overrides since we don't have people using them (local is pretty
> > weak/useless and fail-fast has only ever been used by gcc recipes
> > afaik).
> 
> I've certainly found local useful in the past, though admittedly that
> might have been in the days when it was the highest rather than lowest
> priority OVERRIDE.  You might be right that it isn't a great deal of use
> as it stands.
> 
> I agree that fail-fast should probably go away, but there is an existing
> reference to it in gcc-cross_csl-arm-2008q1.bb and I think the patch
> that removes the OVERRIDE should probably address that usage at the same
> time.
> 
> What's "forcevariable" for?  I don't think we ever had that in oe, and
> there don't seem to be any obvious users of it in oe-core either.

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.

Cheers,

Richard






  reply	other threads:[~2011-05-24 15:11 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 [this message]
2011-05-24 15:15       ` Phil Blundell
2011-05-24 15:24         ` Richard Purdie
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=1306249675.3424.936.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