<div><span style="color: rgb(160, 160, 168); ">On Friday, January 20, 2012 at 1:33 PM, Khem Raj wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On Fri, Jan 20, 2012 at 9:10 AM, Chris Larson <<a href="mailto:kergoth@gmail.com">kergoth@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>On Thu, Jan 19, 2012 at 11:28 PM, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>I added to local.conf</div><div>EXTRA_IMAGE_FEATURES += "tools-debug"</div><div><br></div><div>and now when I do bitbake -g I see that its wanting to build</div><div>"tools-testapp" and "tools-profile"</div><div>even though I did not ask them to be added to my image. all these</div><div>packages are coming from</div><div>single recipe task-core-tools.bb. If I divide this recipe into 3</div><div>different recipes where each provides</div><div>just one task, it then leaves the others out.</div><div><br></div><div>Since these are meta packages they pull in a lot of stuff. Would it be</div><div>ok to divide this recipe</div><div>into 3 individual recipes ? Ideally I would expect that the other</div><div>packages dont get build even</div><div>though they are in same recipe but that is not the case at present</div></div></blockquote><div><br></div><div><br></div><div>One option would be to avoid the task indirection and simply set</div><div>PACKAGE_GROUP_tools-debug = "<list of debug tools>"</div></div></blockquote><div><br></div><div>we do lot of overriding in those tasks it would get</div><div>a bit ugly I guess if we moved that info to image.bbclass</div></div></div></span></blockquote><div><br></div><div>Possibly, but note that it doesn't need to live in a class, either. At mentor, our distro has a .inc that defines a variety of package groups for our images.</div><div><br></div><div>-Chris </div>