From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: adding a single package to an image -- what's the proper way?
Date: Wed, 28 Mar 2012 12:11:49 +0100 [thread overview]
Message-ID: <26662553.TyMenuqT12@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1203280659340.27661@oneiric>
On Wednesday 28 March 2012 07:06:21 Robert P. J. Day wrote:
> On Wed, 28 Mar 2012, Paul Eggleton wrote:
> > On Wednesday 28 March 2012 12:51:46 Marko Katić wrote:
> > > I always use "bitbake -c clean -c cleansstate package" for that purpose.
> >
> > Firstly, cleansstate does a clean already, so no need to specify that as
> > well.
> >
> > Secondly, images are always rebuilt so provided you comment out the
> > IMAGE_INSTALL_append or whatever you have done to change the image
> > contents, you can just build the image again and it will be rebuilt
> > as it was before.
>
> i was testing the various solutions presented, and the first couple
> worked just by changing the local.conf file (both adding and
> removing), but the third using DISTRO_EXTRA_RDEPENDS didn't appear to
> make a difference after i added the appropriate line to local.conf.
>
> if i add the line:
>
> DISTRO_EXTRA_RDEPENDS += "sysfsutils"
>
> do you know if this requires an explicit reconfiguration of some kind
> to be picked up? it's exactly these niggling details i'm trying to
> clarify.
Yes, it will. You would need to clean and rebuild task-base because unlike the
other methods the dependency gets built into a task package.
This is one of the reasons you should not use DISTRO_EXTRA_RDEPENDS from
local.conf - this is intended to be set from the distro configuration only.
Please don't recommend this to be modified from local.conf - stick to
CORE_IMAGE_EXTRA_INSTALL (or IMAGE_INSTALL_append, if you must).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-28 11:20 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
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 [this message]
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=26662553.TyMenuqT12@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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