From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ob0-f175.google.com ([209.85.214.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SCjOL-0006V4-9F for openembedded-core@lists.openembedded.org; Wed, 28 Mar 2012 05:17:45 +0200 Received: by obqv19 with SMTP id v19so792807obq.6 for ; Tue, 27 Mar 2012 20:08:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type; bh=jtJQS9UIKB0tGwzkzm+hrNi9msYR4Zvr+MFq9DgxHJ0=; b=jHfXKut5Sz+z07L0F1kkds+tO//wnS05WY/bJYgUCBk+W6tN0xPQBkM8wEVYyMwNki bl/uqO+GYE/GO/1DNtsltYHwhSYknbW1340RkzZA5gGpmwKzWwizH0NNkVU6wJV12GJA 4NmdILDhfDvBtP1Cgrl7cXgWGalb1Dr/tGWS/xge/3u+ccv3Cg3hNZLTBJO9pUA/Zifi BwttfJSa7JxTdrrqoyoRXTLBoq+PA7bdG4mgEf1HLDWvTf/Ip0EUoKMOlWdKX85LskbG tHi5L44giW1W88qJ6UDEqArWfPpq5fFA8CMFh6i6bZHlqX87vKuCF9ss7oVdBfOMUnDF SC/g== Received: by 10.182.155.68 with SMTP id vu4mr35156494obb.61.1332904122919; Tue, 27 Mar 2012 20:08:42 -0700 (PDT) Received: from frey (ip68-110-79-242.ph.ph.cox.net. [68.110.79.242]) by mx.google.com with ESMTPS id m3sm1517565oem.7.2012.03.27.20.08.41 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 27 Mar 2012 20:08:41 -0700 (PDT) Date: Tue, 27 Mar 2012 20:08:42 -0700 From: Christopher Larson To: Patches and discussions about the oe-core layer Message-ID: In-Reply-To: <20120328024204.GE17470@denix.org> References: <1704770.YM0OKmOcSp@helios> <20120328024204.GE17470@denix.org> X-Mailer: sparrow 1.5 (build 1043.1) MIME-Version: 1.0 Subject: Re: adding a single package to an image -- what's the proper way? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 03:17:45 -0000 Content-Type: multipart/alternative; boundary="4f7280ba_5e884adc_13b26" --4f7280ba_5e884adc_13b26 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline I IMAGE_INSTALL_append or IMAGE_INSTALL_append_pn-core-image-minimal or whatever when I need to quickly add a package temporarily, myself. -- Christopher Larson On Tuesday, March 27, 2012 at 7:42 PM, Denys Dmytriyenko wrote: > On Tue, Mar 27, 2012 at 08:27:02PM +0100, Paul Eggleton wrote: > > On Tuesday 27 March 2012 08:20:11 Robert P. J. Day wrote: > > > i'm currently poring over the OE docs (including the ones at the > > > yocto site), and i'm trying to figure out how to simply add a package > > > to an image through one's local.conf file. > > > > > > the current yocto ref manual has an entire section about customizing > > > images: > > > > > > http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.htm > > > l#usingpoky-extend-customimage > > > > > > but it discusses creating custom recipe files and custom tasks, and > > > using IMAGE_INSTALL and IMAGE_FEATURES and EXTRA_IMAGE_FEATURES, and > > > finally gets into using local.conf, suggesting: > > > > > > DISTRO_EXTRA_RDEPENDS += "strace" > > > > > > is that, in fact, the accepted way if one simply wants to add a > > > package to an existing image build? because as soon as the manual > > > mentions it, in the very next paragraph, it discourages its use. > > > > > > > > > Well, this clearly does not make sense if that's the way it is presented. > > > > The real answer to this question is it depends on why you're adding the > > package. > > > > 1) If you just want to add a single package temporarily for testing, use > > CORE_IMAGE_EXTRA_INSTALL += in local.conf (although I really wish we could > > make this mechanism more generic so that it applies to any image, not just the > > ones in OE-Core). > > > > 2) If you want to add something permanently for every (non-minimal) image > > produced using your DISTRO, set DISTRO_EXTRA_RDEPENDS in your distro > > configuration. This will come into your image via task-distro-base which is > > pulled in by task-base. I don't think we should be advocating doing anything > > with DISTRO_EXTRA_RDEPENDS via local.conf. > > > > 3) If you're adding it permanently for a single image, consider whether adding > > your own custom image recipe would be more appropriate. FWIW, I don't think > > bbappends for recipes are a good idea. > > > > > All these options don't cover one more need - temporarily adding one or more > packages to a single specific image via local.conf. Both option 1) and 2) do > it too broadly to several/all images... And the only option is to go with more > permanent way in 3) by adding own image recipe. > > -- > Denys > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org (mailto:Openembedded-core@lists.openembedded.org) > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > --4f7280ba_5e884adc_13b26 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I IMAGE=5FINSTALL=5Fappend or IMAGE=5FINSTALL=5Fappend=5Fpn-core-imag= e-minimal or whatever when I need to quickly add a package temporarily, m= yself.

-- 
Christopher L= arson

=20

On Tuesday, March 27, = 2012 at 7:42 PM, Denys Dmytriyenko wrote:

On Tue, Mar 27, 2012 at 08:27:02= PM +0100, Paul Eggleton wrote:
On Tuesday 27 March 2012 08:20:11 Robert P. J. Day wrote:
i'm currently poring over the OE docs = (including the ones at the
yocto site), and i'm trying to figur= e out how to simply add a package
to an image through one's loc= al.conf file.

the current yocto ref manual has= an entire section about customizing
images:

l=23usingpoky-extend-customi= mage

but it discusses creating custom recipe fil= es and custom tasks, and
using IMAGE=5FINSTALL and IMAGE=5F=46E= ATURES and EXTRA=5FIMAGE=5F=46EATURES, and
finally gets into us= ing local.conf, suggesting:

DISTRO=5FEXTRA=5FR= DEPENDS +=3D =22strace=22

is that, in fact, the = accepted way if one simply wants to add a
package to an existin= g image build=3F because as soon as the manual
mentions it, in= the very next paragraph, it discourages its use.

Well, this clearly does not make sense if that's the= way it is presented.

The real answer to this q= uestion is it depends on why you're adding the
package.
<= div>
1) If you just want to add a single package temporaril= y for testing, use
CORE=5FIMAGE=5FEXTRA=5FINSTALL +=3D in loca= l.conf (although I really wish we could
make this mechanism mo= re generic so that it applies to any image, not just the
ones = in OE-Core).

2) If you want to add something per= manently for every (non-minimal) image
produced using your DIS= TRO, set DISTRO=5FEXTRA=5FRDEPENDS in your distro
configuratio= n. This will come into your image via task-distro-base which is
pulled in by task-base. I don't think we should be advocating doing any= thing
with DISTRO=5FEXTRA=5FRDEPENDS via local.conf.

3) If you're adding it permanently for a single image, co= nsider whether adding
your own custom image recipe would be mo= re appropriate. =46WIW, I don't think
bbappends for recipes ar= e a good idea.

All these opti= ons don't cover one more need - temporarily adding one or more
packages to a single specific image via local.conf. Both option 1) and 2= ) do
it too broadly to several/all images... And the only opti= on is to go with more
permanent way in 3) by adding own image = recipe.

--
Denys

=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<= /div>
Openembedded-core mailing list
=20 =20 =20 =20 =20

--4f7280ba_5e884adc_13b26--