Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [RFC] Layers, PRINC and bbappends
Date: Wed, 22 May 2013 11:14:14 +0100	[thread overview]
Message-ID: <1369217654.6695.62.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CANyK_8cbVGMQkD7_KEd5KYTBxP+ZT5jY6VVVpdSAv_uY7JPY1w@mail.gmail.com>

On Wed, 2013-05-22 at 09:47 +0100, Paul Barker wrote:
> I've just sent a patch to the yocto@ list to fix this but it's brought
> up two things:
> 
> 1) In openembedded-core/meta/classes/image.bbclass SPLASH is set with
> '?='. I'm overriding this with '=' in
> meta-raspberrypi/conf/machine/raspberrypi.conf which means it can't be
> overridden further in local.conf. Is this worth changing to '??=' in
> image.bbclass, '?=' in the machine conf so that it can be overridden
> with '=' in local.conf? Is my understanding of the overrides correct
> here?

You can always override it from local.conf using a _forcevariable
override (which used to be named "_local", in fact, but that terminology
turned out to be a bit confusing), or a _MACHINE override of course.  So
I don't think there is any major problem here.  

But, that said, it probably is true that the semantics of ??= are less
surprising for users (since it isn't position-dependent in the way
that ?= is) which might make it a better choice for image.bbclass.

p.



  parent reply	other threads:[~2013-05-22 10:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40EC58CA-E878-4F77-8E39-4F8D86F48E29@dominion.thruhere.net>
2013-05-15 20:33 ` [oe] [RFC] Layers, PRINC and bbappends Richard Purdie
2013-05-15 23:02   ` Paul Barker
2013-05-22  8:47     ` Paul Barker
2013-05-22  9:17       ` Martin Jansa
2013-05-22 10:08         ` Paul Eggleton
2013-05-22 10:14       ` Phil Blundell [this message]
2013-05-23  2:50         ` Chris Larson
2013-05-27 12:07           ` Paul Barker
2013-05-16  6:23   ` Koen Kooi
2013-05-16  8:37     ` Paul Eggleton
2013-05-16  9:27       ` Martin Jansa
     [not found] ` <1499979.6pTC18VfFV@helios>
2013-05-16  6:31   ` Koen Kooi
2013-05-16  8:29     ` Paul Eggleton
2013-05-16  8:59       ` Martin Jansa
2013-05-16  9:10         ` Paul Eggleton
2013-05-16  9:29           ` Martin Jansa
2013-05-16 20:15             ` 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=1369217654.6695.62.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    /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