classes/image: write image manifest
authorPaul Eggleton <paul.eggleton@linux.intel.com>
Tue, 26 Nov 2013 12:09:52 +0000 (12:09 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 26 Nov 2013 23:01:32 +0000 (23:01 +0000)
commit0d98fa7c16e7a0cb65d4940c25946b46e1777f91
tree2542cdae73eaca0d57cf33b076243ad8a8b56120
parentfc4c8758b450ab967cd5e75933bd5f59e9e5e4b1
classes/image: write image manifest

Write a list of installed packages to a .manifest file next to the
image, so we can find out what went into the image after it has been
constructed without necessarily having to have buildhistory enabled
(although that will provide more detail.) We can make use of this for
example in the testimage class associated code that checks for installed
packages for determining whether or not to run specific tests.

Note: this replaces the previous ipk-specific manifest code with
something that works for ipk, rpm and deb, and instead of a pruned
status file, packages are listed one per line, in the following format:

<packagename> <packagearch> <version>

Tests for all three backends have shown that the performance impact of
this change is negligible (about 1.5s max).

Implements [YOCTO #5410]

(From OE-Core rev: 2978d1f2617a33e2e3a77e249d73e998d79b4ec9)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/image.bbclass
meta/classes/populate_sdk_deb.bbclass
meta/classes/populate_sdk_ipk.bbclass
meta/classes/populate_sdk_rpm.bbclass
meta/classes/rootfs_ipk.bbclass
scripts/opkg-query-helper.py