From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] [RFC] Layers, PRINC and bbappends
Date: Wed, 22 May 2013 11:08:12 +0100 [thread overview]
Message-ID: <57053358.LVqALflxil@helios> (raw)
In-Reply-To: <20130522091738.GH32431@jama>
On Wednesday 22 May 2013 11:17:38 Martin Jansa wrote:
> On Wed, May 22, 2013 at 09:47:39AM +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 still use:
> SPLASH_forcevariable = "foo"
> SPLASH_your-distro = "foo"
> SPLASH_your-machine = "foo"
> or any other OVERRIDE in local.conf.
This is true; FWIW as the original author of that line in image.bbclass I
wouldn't object to changing it to ??= though.
Having said that, I would note that people are best advised not to try to set
too much from local.conf, especially when it's stuff that affects what is in the
final image. Anyone doing anything moderately custom should really have their
own distro config. FYI, we now have a section in the Yocto Project development
manual documenting this:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-22 10:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:36 [RFC] Layers, PRINC and bbappends Koen Kooi
2013-05-15 14:44 ` Paul Eggleton
2013-05-16 6:31 ` Koen Kooi
2013-05-16 8:29 ` Paul Eggleton
2013-05-16 8:59 ` [OE-core] " Martin Jansa
2013-05-16 9:10 ` Paul Eggleton
2013-05-16 9:29 ` Martin Jansa
2013-05-16 20:15 ` Richard Purdie
2013-05-15 20:33 ` Richard Purdie
2013-05-15 23:02 ` Paul Barker
2013-05-22 8:47 ` Paul Barker
2013-05-22 9:17 ` [OE-core] " Martin Jansa
2013-05-22 10:08 ` Paul Eggleton [this message]
[not found] ` <1369217654.6695.62.camel@phil-desktop.brightsign>
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
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=57053358.LVqALflxil@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
--cc=richard.purdie@linuxfoundation.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