From: Thorsten Scherer <T.Scherer@eckelmann.de>
To: Ralf Glaser <glaser@iotmaxx.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] CRA and SBOM
Date: Tue, 29 Apr 2025 06:46:43 +0200 [thread overview]
Message-ID: <f2blgpcmes5qigyfloypywo7h6464rbq6drivnft6wn6ofshje@7zwrqtnhpwyw> (raw)
In-Reply-To: <BEZP281MB336182C51FD06106E8E2F560A5812@BEZP281MB3361.DEUP281.PROD.OUTLOOK.COM>
Under 'Project Configuration' in ptxdist menuconfig. Availible since
ptxdist-2025.02.0 .
LG
Thorsten
On Mon, Apr 28, 2025 at 02:03:28PM +0000, Ralf Glaser wrote:
> That sounds great, but where do I set PROJECT_DEFAULT_REPORTS?
>
> Ralf
>
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> Von: Michael Olbrich <m.olbrich@pengutronix.de>
> Gesendet: Samstag, 26. April 2025 12:27
> An: Ralf Glaser <glaser@iotmaxx.de>
> Cc: ptxdist@pengutronix.de <ptxdist@pengutronix.de>
> Betreff: Re: [ptxdist] CRA and SBOM
>
> On Fri, Apr 25, 2025 at 01:09:52PM +0000, Ralf Glaser wrote:
> > will there be any support for SBOM generation in ptxdist (as we are all
> > required by the CRA to provide this)?
>
> PTXdist has support to generate SBoMs. It's just not really documented.
>
> Set PROJECT_DEFAULT_REPORTS to "spdx-sbom" and either enable
> PROJECT_GENERATE_REPORTS to generate the SBoM when images are built or run
> "ptxdist make image-reports" to generate them manually.
>
> Michael
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-04-29 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 13:09 Ralf Glaser
2025-04-26 10:27 ` Michael Olbrich
[not found] ` <BEZP281MB336182C51FD06106E8E2F560A5812@BEZP281MB3361.DEUP281.PROD.OUTLOOK.COM>
2025-04-29 4:46 ` Thorsten Scherer [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=f2blgpcmes5qigyfloypywo7h6464rbq6drivnft6wn6ofshje@7zwrqtnhpwyw \
--to=t.scherer@eckelmann.de \
--cc=glaser@iotmaxx.de \
--cc=ptxdist@pengutronix.de \
/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