From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: defining FEATURE_PACKAGES_* in core-image.bbclass vs image.bbclass
Date: Mon, 14 Jul 2014 15:05:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407141457150.14590@localhost> (raw)
i was perusing core-image.bbclass and noticed that the alleged list
of "Available IMAGE_FEATURES" didn't mention "splash" so i was going
to submit a simple patch to add a line for it, before i noticed
something that puzzled me.
i know there are some features that don't correspond to packagegroup
names, and here's one from core-image.bbclass:
FEATURE_PACKAGES_hwcodecs = "${MACHINE_HWCODECS}"
so that feature is clearly a "core image" feature. (i know the
meta-intel layer uses this feature.)
then i noticed that the "splash" feature is defined, not in
core-image.bbclass, but in the more basic image.bbclass, as is
package-management:
FEATURE_PACKAGES_package-management = "${ROOTFS_PKGMANAGE}"
SPLASH ?= "psplash"
FEATURE_PACKAGES_splash = "${SPLASH}"
so is there some rationale for deciding which FEATURE_PACKAGES
settings are defined in core-image, while others are defined in
image?
i'll still add a line for splash to core-image.bbclass.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-14 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 19:05 Robert P. J. Day [this message]
2014-07-14 22:43 ` defining FEATURE_PACKAGES_* in core-image.bbclass vs image.bbclass Rudolf Streif
2014-07-14 23:22 ` Robert P. J. Day
2014-07-15 0:36 ` Rudolf Streif
2014-07-15 0:39 ` Robert P. J. Day
2014-07-15 11:02 ` Robert P. J. Day
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.LFD.2.11.1407141457150.14590@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.