Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Max Krummenacher <max.oss.09@gmail.com>
To: William Delacre <williamdelacre@gmail.com>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: Actually installed packages
Date: Sat, 04 Aug 2018 00:12:51 +0200	[thread overview]
Message-ID: <1533334371.30932.14.camel@gmail.com> (raw)
In-Reply-To: <CAOnRZEJX6vtCikSJK4py2y3r3J-N3fT_tA5FLFYFyPF6vrczjw@mail.gmail.com>

Hi

> What’s the difference between the build/buildhistory/packages content (all
> the packages found here) and the installed-packages.txt file in
> /buildhistory/images/...... ?
> 
> I can see packages in first one which are not included in
> installed-packages.txt

A recipe can provide several packages, usually one with the same
name as the recipe name, then the -dev, -dbg, -doc ... packages,
but a lot of recipes provide additional packages.

An image recipe defines what packages need to be installed in an
image.

Even if your image requires only a part of the packages that a
recipe provides, all packages will be built and will be visible
in build/buildhistory/packages leading to what you describe above.

On top of that, if you built an image which contains different
packages before or bitbaked single recipes then those would also
be seen in the build/buildhistory/packages tree.

Max



  reply	other threads:[~2018-08-03 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 21:31 Actually installed packages William Delacre
2018-08-03 22:12 ` Max Krummenacher [this message]
2018-08-04 12:12   ` William Delacre
2018-08-04 14:19     ` William Delacre
2018-08-05 10:56       ` Max Krummenacher

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=1533334371.30932.14.camel@gmail.com \
    --to=max.oss.09@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=williamdelacre@gmail.com \
    /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