Patchwork [bitbake-devel,0/1] print which pkgs would be built

login
register
mail settings
Submitter Robert Yang
Date June 21, 2012, 2:28 a.m.
Message ID <cover.1340179047.git.liezhi.yang@windriver.com>
Download mbox
Permalink /patch/30371/
State New
Headers show

Pull-request

git://git.pokylinux.org/poky-contrib robert/buildlist

Comments

Robert Yang - June 21, 2012, 2:28 a.m.
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(-)