From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH 0/1] print which pkgs would be built
Date: Thu, 21 Jun 2012 10:28:53 +0800 [thread overview]
Message-ID: <cover.1340179047.git.liezhi.yang@windriver.com> (raw)
Hi Paul,
This is for:
* The ability to know what pkgs will be *compiled* for a given image.
For the "installed" part, use the core-image-sato as an example, which
will install 395 rpm binary pkgs:
Note:
The following ones has filtered out the "-dev/-dbg/-staticdev/-natives":
1) If we only grab the RDEPENDS, there are only 342 pkgs, which is less
than 395
2) If we grab both the RDEPENDS and RRECOMMENDS, there are 476 pkgs,
which is more than 395
The problem is that there is a RCONFLICTS, the RRECOMMENDS and
RCONFLICTS will be used by the package manager to determine which pkg
would be installed, this makes it hard to predict the pkg that will be
installed.
// Robert
The following changes since commit e0a70547069fe7e8a2d6bdaffc985fb172d46c31:
perl: Allow perl to cross build and native build in a directory named "t" (2012-06-18 17:33:04 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/buildlist
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/buildlist
Robert Yang (1):
print which pkgs would be built
bitbake/bin/bitbake | 2 +-
bitbake/lib/bb/cooker.py | 4 ++++
2 files changed, 5 insertions(+), 1 deletions(-)
next reply other threads:[~2012-06-21 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 2:28 Robert Yang [this message]
2012-06-21 2:28 ` [PATCH 1/1] print which pkgs would be built Robert Yang
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=cover.1340179047.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=bitbake-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.