was reminded of this as i was perusing some old OE core notes.
remember this from core-image.bbclass?
CORE_IMAGE_BASE_INSTALL = '\
task-core-boot \
task-base-extended \
\
${CORE_IMAGE_EXTRA_INSTALL} \
'
CORE_IMAGE_EXTRA_INSTALL ?= ""
IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
except there are some core image variation recipes
(core-image-minimal-dev.bb, among others) that do things like this:
IMAGE_INSTALL = "task-core-boot ${ROOTFS_PKGMANAGE}"
IMAGE_FEATURES += "dev-pkgs"
IMAGE_LINGUAS = " "
LICENSE = "MIT"
inherit core-image
note how the explicit assignment to IMAGE_INSTALL in that second
example will copletely override the "IMAGE_INSTALL ?=" in the bbclass
file, at which point ${CORE_IMAGE_EXTRA_INSTALL} will obviously never
be evaluated and included.
i'm guessing that's exactly what the developer had in mind, but it
seems that has the potential to be really misleading, since a newcomer
might want to create an image based on, say,
core-image-minimal-dev.bb, and *think* that, since it's a variation of
a core image recipe, he can use CORE_IMAGE_EXTRA_INSTALL to add extra
packages to the image. which clearly won't work.
i'm sure numerous people will point out that the above works
perfectly well as long as you understand what's going on. i'm just
suggesting that, sooner or later, someone is going to waste a
considerable amount of time trying to figure out why nothing they
specify with CORE_IMAGE_EXTRA_INSTALL is being added to their image.
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
