From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] SBOM / manifest
Date: Tue, 5 Oct 2021 19:19:53 +0200 [thread overview]
Message-ID: <b5834921-b6dc-8675-2cba-b4beb01cc320@t2data.com> (raw)
In-Reply-To: <20211005135815.dalyv3zl6i7737yk@falbala.internal.home.lespocky.de>
On 10/5/21 15:58, Alexander Dahl wrote:
> Hei hei,
>
> On Tue, Oct 05, 2021 at 09:38:55AM -0400, Akshay Bhat wrote:
>> Is there a way of generating a SBOM (Software Bill of Materials) i.e.
>> list all the software packages installed on the target with the
>> associated version and license info for a ptx-dist? Something similar
>> 'make legal-info' in buildroot.
>
> You can generate a license report like this:
>
> ptxdist make license-report
>
> You'll find the report in platform-foo/report as .pdf afterwards.
>
>> The closest I could find was:
>> ptxdist list-packages | xargs ptxdist package-info | grep -e package:
>> -e version: -e license:
>>
>> Also are there any plans in the roadmap for supporting a SPDX SBOM?
I'd second an implementation of a SPDX export of package usage, licence,
patch modifications and link dependencies.
It's much more usable with something like SPDX instead of a pdf.
>
> Not sure. But the documentation has some hints:
>
> https://www.ptxdist.org/doc/dev_licenses.html
>
> HTH & Greets
> Alex
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-10-05 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 13:38 Akshay Bhat
2021-10-05 13:58 ` Alexander Dahl
2021-10-05 14:05 ` Michael Olbrich
2021-10-05 17:22 ` Akshay Bhat
2021-10-05 17:19 ` Christian Melki [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=b5834921-b6dc-8675-2cba-b4beb01cc320@t2data.com \
--to=christian.melki@t2data.com \
--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