<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 12, 2013 at 4:24 AM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":em" style="overflow:hidden"> wait, i think i might have just answered my own question ... see<br>
below ...<br>
<div><div class="h5"><br>
On Sat, 12 Oct 2013, Robert P. J. Day wrote:<br>
<br>
> just to make sure i'm not missing anything subtle, i know you can<br>
> add a "packagegroup" to your build using IMAGE_FEATURES, but given<br>
> that there are *lots* more packagegroup recipe files in oe-core than<br>
> have corresponding PACKAGE_GROUP_* definitions in core-image.bbclass:<br>
><br>
> $ find . -name "packagegroup*bb"<br>
> ./recipes-gnome/packagegroups/<a href="http://packagegroup-core-standalone-gmae-sdk-target.bb" target="_blank">packagegroup-core-standalone-gmae-sdk-target.bb</a><br>
> ./recipes-gnome/packagegroups/<a href="http://packagegroup-toolset-native.bb" target="_blank">packagegroup-toolset-native.bb</a><br>
> ./recipes-gnome/packagegroups/<a href="http://packagegroup-core-sdk-gmae.bb" target="_blank">packagegroup-core-sdk-gmae.bb</a><br>
> ./recipes-devtools/packagegroups/<a href="http://packagegroup-core-device-devel.bb" target="_blank">packagegroup-core-device-devel.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-cross-canadian.bb" target="_blank">packagegroup-cross-canadian.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-sdk.bb" target="_blank">packagegroup-core-sdk.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-ssh-openssh.bb" target="_blank">packagegroup-core-ssh-openssh.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-standalone-sdk-target.bb" target="_blank">packagegroup-core-standalone-sdk-target.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-boot.bb" target="_blank">packagegroup-core-boot.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-tools-profile.bb" target="_blank">packagegroup-core-tools-profile.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-self-hosted.bb" target="_blank">packagegroup-self-hosted.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-ssh-dropbear.bb" target="_blank">packagegroup-core-ssh-dropbear.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-tools-debug.bb" target="_blank">packagegroup-core-tools-debug.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-buildessential.bb" target="_blank">packagegroup-core-buildessential.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-tools-testapps.bb" target="_blank">packagegroup-core-tools-testapps.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-base.bb" target="_blank">packagegroup-base.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-nfs.bb" target="_blank">packagegroup-core-nfs.bb</a><br>
> ./recipes-core/packagegroups/<a href="http://packagegroup-core-eclipse-debug.bb" target="_blank">packagegroup-core-eclipse-debug.bb</a><br>
> ./recipes-graphics/packagegroups/<a href="http://packagegroup-core-x11.bb" target="_blank">packagegroup-core-x11.bb</a><br>
> ./recipes-graphics/packagegroups/<a href="http://packagegroup-core-x11-base.bb" target="_blank">packagegroup-core-x11-base.bb</a><br>
> ./recipes-graphics/packagegroups/<a href="http://packagegroup-core-x11-xserver.bb" target="_blank">packagegroup-core-x11-xserver.bb</a><br>
> ./recipes-graphics/packagegroups/<a href="http://packagegroup-core-clutter.bb" target="_blank">packagegroup-core-clutter.bb</a><br>
> ./recipes-graphics/packagegroups/<a href="http://packagegroup-core-directfb.bb" target="_blank">packagegroup-core-directfb.bb</a><br>
> ./recipes-qt/packagegroups/<a href="http://packagegroup-qte-toolchain-target.bb" target="_blank">packagegroup-qte-toolchain-target.bb</a><br>
> ./recipes-qt/packagegroups/<a href="http://packagegroup-core-qt4e.bb" target="_blank">packagegroup-core-qt4e.bb</a><br>
> ./recipes-qt/packagegroups/<a href="http://packagegroup-qt-toolchain-target.bb" target="_blank">packagegroup-qt-toolchain-target.bb</a><br>
> ./recipes-qt/packagegroups/<a href="http://packagegroup-core-qt.bb" target="_blank">packagegroup-core-qt.bb</a><br>
> ./recipes-sato/packagegroups/<a href="http://packagegroup-core-x11-sato.bb" target="_blank">packagegroup-core-x11-sato.bb</a><br>
> ./recipes-extended/packagegroups/<a href="http://packagegroup-core-lsb.bb" target="_blank">packagegroup-core-lsb.bb</a><br>
> ./recipes-extended/packagegroups/<a href="http://packagegroup-core-basic.bb" target="_blank">packagegroup-core-basic.bb</a><br>
> $<br>
><br>
> is it accurate to say that you can just as equivalently add the recipe<br>
> file directly using, say, CORE_IMAGE_EXTRA_INSTALL? is there any<br>
> functional difference between those two approaches?<br>
<br>
</div></div> feeling a bit sheepish if this is the answer ... i notice that<br>
core-image.bbclass defines:<br>
<br>
PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"<br>
<br>
however, while there is no recipe file named<br>
"<a href="http://packagegroup-core-nfs-server.bb" target="_blank">packagegroup-core-nfs-server.bb</a>", there is one named<br>
"<a href="http://packagegroup-core-nfs.bb" target="_blank">packagegroup-core-nfs.bb</a>", which contains:<br>
<br>
inherit packagegroup<br>
<br>
PACKAGES = "${PN}-server"<br>
<br>
so does defining a PACKAGE_GROUP_* entry in core-image.bbclass allow<br>
the packagegroup definition search to examine the internals of a<br>
recipe file to check the definition of "PACKAGES" to find a match? as<br>
opposed to referring to a recipe file directly</div></blockquote></div><br>PACKAGE_GROUP_<some group that can be listed in IMAGE_FEATURES> = "<a list of binary packages, just as you'd add to IMAGE_INSTALL or CORE_IMAGE_EXTRA_INSTALL yourself>"</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">That's all there is to it. packagegroup-core-nfs-server is a binary package. PACKAGE_GROUP_nfs-server accepts lists of binary packages, not lists of recipes.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Things got a bit more confusing once tasks got renamed to packagegroups, as the pure data driven package grouping mechanism (PACKAGE_GROUP) already existed at that time.<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>