From: Uladzimir Bely <ubely@ilbers.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com
Subject: Re: [PATCH] debianize: Introduce DEBIAN_MULTI_ARCH
Date: Wed, 01 Nov 2023 10:13:10 +0300 [thread overview]
Message-ID: <042ed6698af8c6a102a3d98dff75cba9d1d153f9.camel@ilbers.de> (raw)
In-Reply-To: <20231026150012.1396190-1-florian.bezdeka@siemens.com>
On Thu, 2023-10-26 at 17:00 +0200, 'Florian Bezdeka' via isar-users
wrote:
> Allow setting the Multi-Arch field for auto generated control files.
> The
> default is set to "no" which is the pre-multiarch behavior.
>
> Recipes can simply overwrite the Multi-Arch field now by defining the
> DEBIAN_MULTI_ARCH variable.
>
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
> meta/classes/debianize.bbclass | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/classes/debianize.bbclass
> b/meta/classes/debianize.bbclass
> index f6ce11a2..16f3638d 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -9,6 +9,7 @@ DPKG_ARCH ??= "any"
> DEBIAN_BUILD_DEPENDS ??= ""
> DEBIAN_DEPENDS ??= ""
> DEBIAN_CONFLICTS ??= ""
> +DEBIAN_MULTI_ARCH ??= "no"
> DESCRIPTION ??= "must not be empty"
> MAINTAINER ??= "Unknown maintainer <unknown@example.com>"
>
> @@ -77,6 +78,7 @@ Package: ${BPN}
> Architecture: ${DPKG_ARCH}
> Depends: ${DEBIAN_DEPENDS}
> Conflicts: ${DEBIAN_CONFLICTS}
> +Multi-Arch: ${DEBIAN_MULTI_ARCH}
> Description: ${DESCRIPTION}
> EOF
> }
> --
> 2.41.0
>
Applied to next, thanks.
prev parent reply other threads:[~2023-11-01 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:00 Florian Bezdeka
2023-10-30 2:30 ` MOESSBAUER, Felix
2023-11-01 7:13 ` Uladzimir Bely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=042ed6698af8c6a102a3d98dff75cba9d1d153f9.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox