[PATCH 1/1] always add architecture to binary packages in manifest

[Felix Moessbauer]

The manifest file contains the source / binary package relation and is
helpful for license clearing. However, the binary package is only
annotated with an architecture specified (:<arch>) if it otherwise
cannot be uniquely identified on the generating system. As the consumer
of that data is on a different system, this is not helpful. We now
explicitly add the architecture specifier so that downstream consumers
do not have to guess.

Despite this slightly changes the output format, we don't consider this
a breaking change, as the downstream consume anyways could not know
which packages get the architecture specifier and which not, as this
only depends on the package list of the target rootfs.

Signed-off-by: Felix Moessbauer <felix.mo...@siemens.com>
---
meta/classes/rootfs.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
index 12227db1..65779248 100644
--- a/meta/classes/rootfs.bbclass
+++ b/meta/classes/rootfs.bbclass
@@ -399,7 +399,7 @@ rootfs_generate_manifest () {
mkdir -p ${ROOTFS_MANIFEST_DEPLOY_DIR}
sudo -E chroot --userspec=$(id -u):$(id -g) '${ROOTFSDIR}' \
dpkg-query -W -f \
- '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' > \
+ '${source:Package}|${source:Version}|${Package}:${Architecture}|${Version}\n' > \
'${ROOTFS_MANIFEST_DEPLOY_DIR}'/'${ROOTFS_PACKAGE_SUFFIX}'.manifest
}

--
2.51.0