From: Denys Dmytriyenko <denis@denix.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: adding a single package to an image -- what's the proper way?
Date: Tue, 27 Mar 2012 22:42:04 -0400 [thread overview]
Message-ID: <20120328024204.GE17470@denix.org> (raw)
In-Reply-To: <1704770.YM0OKmOcSp@helios>
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
next prev parent reply other threads:[~2012-03-28 2:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 12:20 adding a single package to an image -- what's the proper way? Robert P. J. Day
2012-03-27 12:56 ` Marko Katić
2012-03-27 19:12 ` Robert P. J. Day
2012-03-27 19:27 ` Paul Eggleton
2012-03-28 2:42 ` Denys Dmytriyenko [this message]
2012-03-28 3:08 ` Christopher Larson
2012-03-28 9:32 ` Robert P. J. Day
2012-03-28 9:35 ` Robert P. J. Day
2012-03-28 10:51 ` Marko Katić
2012-03-28 10:57 ` Paul Eggleton
2012-03-28 11:06 ` Robert P. J. Day
2012-03-28 11:11 ` Paul Eggleton
2012-03-28 11:14 ` Robert P. J. Day
2012-03-28 11:22 ` Paul Eggleton
2012-03-28 13:18 ` Robert P. J. Day
2012-03-28 13:19 ` Andrea Adami
2012-03-28 18:55 ` Paul Eggleton
2012-03-28 13:48 ` Koen Kooi
2012-03-28 13:50 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120328024204.GE17470@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox