<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 3:26 PM, Chris Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>p.s. as with other things i've put on my wish list, it would be great<br>
if a variation of bitbake could list the available package groups.</div></blockquote><div><br></div></div><div>Depending on whether you want the metadata package groups or the packages: </div></div><br>bitbake -e <some core-image inheriting recipe> | grep PACKAGE_GROUP_</blockquote>
</div><br>Erm, wrong button. To continue: or..</div><div class="gmail_extra"><br></div><div class="gmail_extra">bitbake -s | grep packagegroup-</div><div class="gmail_extra"><br></div><div class="gmail_extra">Also, to comment on something tangentially related from a different thread, technically the PACKAGE_GROUP_ variables were the first to use the term as far as I'm aware. *tasks* were then renamed to use that name as well, which is where a bunch of the confusion probably got introduced.</div>
<div class="gmail_extra">-- <br>Christopher Larson<br>
</div>