From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] SBOM / manifest
Date: Tue, 5 Oct 2021 15:58:15 +0200 [thread overview]
Message-ID: <20211005135815.dalyv3zl6i7737yk@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <CACrMeVDxKeB-was3w9qcWJyq-Ui7MMS2ow4qbPmOGm-Se-J=SA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]
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?
Not sure. But the documentation has some hints:
https://www.ptxdist.org/doc/dev_licenses.html
HTH & Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-10-05 13:58 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 [this message]
2021-10-05 14:05 ` Michael Olbrich
2021-10-05 17:22 ` Akshay Bhat
2021-10-05 17:19 ` Christian Melki
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=20211005135815.dalyv3zl6i7737yk@falbala.internal.home.lespocky.de \
--to=post@lespocky.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