<div style="font-family: Helvetica; font-size: 13px; ">I IMAGE_INSTALL_append or IMAGE_INSTALL_append_pn-core-image-minimal or whatever when I need to quickly add a package temporarily, myself.<br></div>
<div><div><br></div><div>-- </div><div>Christopher Larson</div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, March 27, 2012 at 7:42 PM, Denys Dmytriyenko wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On Tue, Mar 27, 2012 at 08:27:02PM +0100, Paul Eggleton wrote:</div><blockquote type="cite"><div><div>On Tuesday 27 March 2012 08:20:11 Robert P. J. Day wrote:</div><blockquote type="cite"><div><div> i'm currently poring over the OE docs (including the ones at the</div><div>yocto site), and i'm trying to figure out how to simply add a package</div><div>to an image through one's local.conf file.</div><div><br></div><div> the current yocto ref manual has an entire section about customizing</div><div>images:</div><div><br></div><div><a href="http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.htm">http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.htm</a></div><div>l#usingpoky-extend-customimage</div><div><br></div><div>but it discusses creating custom recipe files and custom tasks, and</div><div>using IMAGE_INSTALL and IMAGE_FEATURES and EXTRA_IMAGE_FEATURES, and</div><div>finally gets into using local.conf, suggesting:</div><div><br></div><div> DISTRO_EXTRA_RDEPENDS += "strace"</div><div><br></div><div>is that, in fact, the accepted way if one simply wants to add a</div><div>package to an existing image build? because as soon as the manual</div><div>mentions it, in the very next paragraph, it discourages its use.</div></div></blockquote><div><br></div><div>Well, this clearly does not make sense if that's the way it is presented. </div><div><br></div><div>The real answer to this question is it depends on why you're adding the </div><div>package.</div><div><br></div><div>1) If you just want to add a single package temporarily for testing, use </div><div>CORE_IMAGE_EXTRA_INSTALL += in local.conf (although I really wish we could </div><div>make this mechanism more generic so that it applies to any image, not just the </div><div>ones in OE-Core).</div><div><br></div><div>2) If you want to add something permanently for every (non-minimal) image </div><div>produced using your DISTRO, set DISTRO_EXTRA_RDEPENDS in your distro </div><div>configuration. This will come into your image via task-distro-base which is </div><div>pulled in by task-base. I don't think we should be advocating doing anything </div><div>with DISTRO_EXTRA_RDEPENDS via local.conf.</div><div><br></div><div>3) If you're adding it permanently for a single image, consider whether adding </div><div>your own custom image recipe would be more appropriate. FWIW, I don't think </div><div>bbappends for recipes are a good idea.</div></div></blockquote><div><br></div><div>All these options don't cover one more need - temporarily adding one or more </div><div>packages to a single specific image via local.conf. Both option 1) and 2) do </div><div>it too broadly to several/all images... And the only option is to go with more </div><div>permanent way in 3) by adding own image recipe.</div><div><br></div><div>-- </div><div>Denys</div><div><br></div><div>_______________________________________________</div><div>Openembedded-core mailing list</div><div><a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a></div><div><a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>