From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: setting EXTRA_IMAGE_FEATURES explicitly in .bb file can screw things up
Date: Mon, 9 Jul 2012 12:25:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207091224240.1542@oneiric> (raw)
In-Reply-To: <1803032.sCdKSRoOHk@helios>
On Mon, 9 Jul 2012, Paul Eggleton wrote:
> On Monday 09 July 2012 11:24:27 Robert P. J. Day wrote:
> > On Mon, 9 Jul 2012, Andrei Gherzan wrote:
> > > So IMHO the EXTRA_IMAGE_FEATURES variable in the image should be
> > > merged in the IMAGE_FEATURES above. I don't see the meaning of it.
> >
> > yup, that was precisely the point i was making. so given the
> > potential for confusion, what should be the "best practise" here?
> > based on my sketchy understanding, it seems the proper approach would
> > be to let recipe files use IMAGE_FEATURES exclusively, while
> > specifically reserving EXTRA_IMAGE_FEATURES for the developer's
> > local.conf file, and avoid the current unpleasant mixing.
>
> Sounds like a good idea to me.
i'll send in a patch that does that, especially since
local.conf.sample specifically instructs the developer to use
EXTRA_IMAGE_FEATURES. patch coming shortly.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2012-07-09 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 18:52 setting EXTRA_IMAGE_FEATURES explicitly in .bb file can screw things up Robert P. J. Day
2012-07-08 18:06 ` Robert P. J. Day
2012-07-09 8:59 ` Andrei Gherzan
2012-07-09 15:24 ` Robert P. J. Day
2012-07-09 15:30 ` Paul Eggleton
2012-07-09 16:25 ` Robert P. J. Day [this message]
2012-07-09 20:32 ` Andrei Gherzan
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=alpine.DEB.2.02.1207091224240.1542@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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