public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Quentin Schulz via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 6/8] utils/generate-cyclonedx: mark host packages as external
Date: Thu, 9 Apr 2026 14:58:53 +0200	[thread overview]
Message-ID: <de0bb761-ca88-4bc6-8d7b-6bd14e9d1cbe@cherry.de> (raw)
In-Reply-To: <20260311140457.140041-7-thomas.perale@mind.be>

Hi Thomas,

On 3/11/26 3:04 PM, Thomas Perale via buildroot wrote:
> Mark Buildroot's host packages as 'external' with the 'isExternal'
> property. Starting CycloneDX v1.7 [1][2] the CycloneDX spec defines this
> property like the following [3].
> 
>> An external component is one that is not part of an assembly, but is
>> expected to be provided by the environment, regardless of the
>> component's .scope. This setting can be useful for distinguishing which
>> components are bundled with the product and which can be relied upon to
>> be present in the deployment environment.
> 
> This fits the usage of 'host' packages : a package provided by the
> environment and not bundled with the target.
> 

That's not my understanding. None of the examples provided in the GitHub 
issue match a requirement on host executables (in the context of 
cross-compilation). They all are related to runtime dependencies 
(dynamic linking, interpreters, hardware-limitation (which SoC/CPU can 
this run on)) you need to use with the binary(ies) associated with that 
SBOM. What Buildroot generates is likely self-sufficient? A Buildroot 
SDK is kinda different, but then the host packages wouldn't be external 
anyway since they would be part of the SDK and thus "internal". Do you 
have a different reading of the spec on this? (We just started to look 
at CycloneDX generated by Buildroot so I wouldn't trust my own 
gut-feeling on that :) ).

> [1] https://github.com/CycloneDX/specification/releases/tag/1.7
> [2] https://cyclonedx.org/docs/1.7/json/#components_items_isExternal
> [3] https://github.com/CycloneDX/specification/issues/321
> 
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
>   utils/generate-cyclonedx | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/utils/generate-cyclonedx b/utils/generate-cyclonedx
> index cbce3364de..35d8c72057 100755
> --- a/utils/generate-cyclonedx
> +++ b/utils/generate-cyclonedx
> @@ -373,6 +373,9 @@ class CycloneDX:
>           return {
>               "bom-ref": name,
>               "type": "library",
> +            **({
> +                "isExternal": True
> +            } if self.options.cyclonedx_version >= (1, 7) and comp["type"] == "host" else {}),
>               **({
>                   "name": comp["name"],
>               } if "name" in comp else {}),

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-04-09 12:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 14:04 [Buildroot] [PATCH v5 0/8] Support CycloneDX v1.7 Thomas Perale via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 1/8] utils/generate-cyclonedx: use tuple for version Thomas Perale via buildroot
2026-04-09 12:08   ` Quentin Schulz via buildroot
2026-04-09 20:27     ` Thomas Perale via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 2/8] utils/generate-cyclonedx: move license download in a function Thomas Perale via buildroot
2026-04-09 12:12   ` Quentin Schulz via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 3/8] utils/generate-cyclonedx: move utility function Thomas Perale via buildroot
2026-04-09 12:27   ` Quentin Schulz via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 4/8] utils/generate-cyclonedx: encapsulate CycloneDX generation functions Thomas Perale via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 5/8] utils/generate-cyclonedx: optional bump to v1.7 Thomas Perale via buildroot
2026-04-09 12:40   ` Quentin Schulz via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 6/8] utils/generate-cyclonedx: mark host packages as external Thomas Perale via buildroot
2026-04-09 12:58   ` Quentin Schulz via buildroot [this message]
2026-04-09 20:42     ` Thomas Perale via buildroot
2026-04-09 20:43       ` Thomas Perale via buildroot
2026-04-10  9:12         ` Quentin Schulz via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 7/8] utils/generate-cyclonedx: add 'id' property to resolves Thomas Perale via buildroot
2026-04-09 13:22   ` Quentin Schulz via buildroot
2026-04-09 20:24     ` Thomas Perale via buildroot
2026-03-11 14:04 ` [Buildroot] [PATCH v5 8/8] utils/generate-cyclonedx: split vulnerabilities per state Thomas Perale via buildroot

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=de0bb761-ca88-4bc6-8d7b-6bd14e9d1cbe@cherry.de \
    --to=buildroot@buildroot.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.perale@mind.be \
    /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