Bug 5025 - Query the package list built by an image
Summary: Query the package list built by an image
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-08-20 15:29 UTC by Laszlo Papp
Modified: 2016-04-13 15:35 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laszlo Papp 2013-08-20 15:29:51 UTC
It would be nice to use this feature for briefly checking out what packages will be available after an image build, e.g. core-image-minimal.

This can possibly be done by enabling the build history, asking for the dependency tree and so forth, but none feels really "native" about getting only the information you need.

Today, I just came across again to check if a package was available for an image (core-image-minimal in this particular scenario), but I have no simple way to do so as of today.
Comment 1 Ross Burton 2013-08-20 15:31:41 UTC
I presume the request is the package list *to be installed* in the image.  This is a subset of the packages built by an image target (native tools, etc).

"bitbake -e [imagename] | grep IMAGE_INSTALL=" is *almost* what you want, apart from that the bulk of that list will be package groups and need re-expanding.
Comment 2 Ross Burton 2016-04-13 15:35:18 UTC
We now deploy a full package manifest alongside the image.