From: Zhihang Wei <wzh@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Cc: felix.moessbauer@siemens.com
Subject: Re: [PATCH v2] debianize: add support for DEBIAN_BUILT_USING
Date: Thu, 23 Oct 2025 17:31:47 +0200 [thread overview]
Message-ID: <45cb0358-899a-4192-8728-ea4648114c27@ilbers.de> (raw)
In-Reply-To: <20251010104344.4144183-1-srinuvasan.a@siemens.com>
v2 was applied to next, thanks.
Best regards,
Zhihang
On 10/10/25 12:43, srinuvasan.a via isar-users wrote:
> From: srinuvasan<srinuvasan.a@siemens.com>
>
> This field is particularly important when creating a derivative of an upstream package (f.e: bmap-tools),
> as SBOM tools (such as the proposed debsbom) can detect it and record the original package as a dependency
>
> Typically, this field declares that a binary package incorporates parts from another source package or binary
> With this update, Built-Using can be set directly in debian/control using the DEBIAN_BUILT_USING variable
>
> Examples:
>
> A package using the source code from the gcc-4.6-source package:
> Built-Using: gcc-4.6 (= 4.6.0-11)
>
> A package including binaries from grub2 and loadlin:
> Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
>
> Recipes can now simply define DEBIAN_BUILT_USING to populate this field automatically
>
> Note: Several upstream packages define this field, for example shim-signed, fwupd, and grub-efi-amd64-bin.
>
> Signed-off-by: srinuvasan<srinuvasan.a@siemens.com>
> ---
> doc/user_manual.md | 3 +++
> meta/classes/debianize.bbclass | 3 +++
> 2 files changed, 6 insertions(+)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index 67f91973..4b5e0843 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -1006,6 +1006,9 @@ Other (optional) customization variables include:
> - `DEBIAN_PROVIDES` - declare a virtual package to satisfy dependencies
> - `DEBIAN_REPLACES` - to replace a package with another
> - `DEBIAN_BREAKS` - Packages which break other packages
> + - `DEBIAN_BUILT_USING` - Used when a binary package includes parts of other source packages, f.e: by statically linking their libraries or embedding their
> + code or data during the build.
> + E.x: Built-Using: <name> (= <version>)
>
> ### Prebuilt .deb packages from somewhere
>
> diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
> index 4989c601..9197bc25 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -13,6 +13,7 @@ DEBIAN_PROVIDES ??= ""
> DEBIAN_REPLACES ??= ""
> DEBIAN_CONFLICTS ??= ""
> DEBIAN_BREAKS ??= ""
> +DEBIAN_BUILT_USING ??= ""
> DEBIAN_MULTI_ARCH ??= "no"
> DEBIAN_COMPAT ??= "10"
> DEBIAN_CHANGELOG_TIMESTAMP ??= "3600"
> @@ -74,6 +75,7 @@ deb_create_control[vardeps] += "DEBIANIZE_BUILD_DEPENDS \
> DEBIAN_PROVIDES \
> DEBIAN_REPLACES \
> DEBIAN_BREAKS \
> + DEBIAN_BUILT_USING \
> DEBIAN_CONFLICTS"
> deb_create_control() {
> cat << EOF > ${S}/debian/control
> @@ -90,6 +92,7 @@ Depends: ${@ deb_list_beautify(d, 'DEBIAN_DEPENDS')}
> Provides: ${@ deb_list_beautify(d, 'DEBIAN_PROVIDES')}
> Replaces: ${@ deb_list_beautify(d, 'DEBIAN_REPLACES')}
> Breaks: ${@ deb_list_beautify(d, 'DEBIAN_BREAKS')}
> +Built-Using: ${@ deb_list_beautify(d, 'DEBIAN_BUILT_USING')}
> Conflicts: ${@ deb_list_beautify(d, 'DEBIAN_CONFLICTS')}
> Multi-Arch: ${DEBIAN_MULTI_ARCH}
> Description: ${DESCRIPTION}
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/45cb0358-899a-4192-8728-ea4648114c27%40ilbers.de.
prev parent reply other threads:[~2025-10-23 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 8:27 [PATCH] " srinuvasan.a via isar-users
2025-10-10 9:00 ` 'MOESSBAUER, Felix' via isar-users
2025-10-10 10:43 ` [PATCH v2] " srinuvasan.a via isar-users
2025-10-23 15:31 ` Zhihang Wei [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=45cb0358-899a-4192-8728-ea4648114c27@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.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