[PATCH 1/1] container-loader: make generated package arch specific

[Felix Moessbauer]

The generated package contains files which are architecture specific
(the container image). By that, it must not be arch=all. Further, we
currently cannot co-install the package for multiple architectures and
we also do not want to automatically allow resolving this package in a
foreign architecture. Hence set the multi-arch specifier to "allowed",
which means the dependency needs to be annotated with ":any".

Signed-off-by: Felix Moessbauer <felix.mo...@siemens.com>
---
meta/recipes-support/container-loader/container-loader.inc | 3 +++
1 file changed, 3 insertions(+)

diff --git a/meta/recipes-support/container-loader/container-loader.inc b/meta/recipes-support/container-loader/container-loader.inc
index 5fd8d23c..90c16228 100644
--- a/meta/recipes-support/container-loader/container-loader.inc
+++ b/meta/recipes-support/container-loader/container-loader.inc
@@ -11,6 +11,9 @@ SRC_URI += " \
file://container-loader.service.tmpl \
file://container-loader.sh.tmpl"

+DPKG_ARCH ?= "${DISTRO_ARCH}"
+DEBIAN_MULTI_ARCH ?= "allowed"
+
CONTAINER_DELETE_AFTER_LOAD ?= "0"

DEBIAN_DEPENDS += "${CONTAINER_ENGINE_PACKAGES}, zstd"
--
2.39.5

[Uladzimir Bely]

On Wed, 2025-03-12 at 14:50 +0100, 'Felix Moessbauer' via isar-users
wrote:

Applied to next, thanks.

--
Best regards,
Uladzimir.