From patchwork Thu Jun 21 02:28:53 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [bitbake-devel,0/1] print which pkgs would be built Date: Thu, 21 Jun 2012 02:28:53 -0000 From: Robert Yang X-Patchwork-Id: 30371 Message-Id: To: Cc: Zhenfeng.Zhao@windriver.com 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(-)