From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Christian Stewart <christian@aperture.us>,
Arnout Vandecappelle <arnout@rnout.be>
Subject: Re: [Buildroot] [PATCH 0/7] Add PURL support
Date: Wed, 16 Apr 2025 21:07:38 +0200 [thread overview]
Message-ID: <87tt6o3oxx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250415195547.199428-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Tue, 15 Apr 2025 21:55:33 +0200")
>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:
> This patch series add support for the PURL.
> https://github.com/package-url/purl-spec
Nice!
> PURL are a software identifier similar to CPE.
> More information on PURL can be found in the first patch of the series.
> After testing the usage of PURL with DependencyTrack and
> https://ossindex.sonatype.org I can see that it improves the tracking
> of CVEs and version bump
Out of interest, how does it help (do you have an example?)
Does a PURL match complicate anything if we add a local (security) patch
to a package?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-16 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 19:55 [Buildroot] [PATCH 0/7] Add PURL support Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 1/7] package/pkg-generic.mk: add PURL package variable Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 2/7] package/pkg-download: add 'owner' macro Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 2/7] package/pkg-download: add repository macro Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 3/7] package/pkg-golang: support PURL generation Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 4/7] package/pkg-cargo: " Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 5/7] package/pkg-perl: " Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 6/7] package/pkg-python: " Thomas Perale via buildroot
2025-04-15 19:55 ` [Buildroot] [PATCH 7/7] package/pkg-utils: add PURL to show-info output Thomas Perale via buildroot
2025-04-16 19:07 ` Peter Korsgaard [this message]
2025-04-16 19:19 ` [Buildroot] [PATCH 0/7] Add PURL support Arnout Vandecappelle via buildroot
[not found] ` <4b029329-2258-428d-80c9-315dbd6335be@essensium.com>
2025-04-16 19:58 ` Thomas Petazzoni via buildroot
2025-04-16 20:06 ` Thomas Perale via buildroot
2025-04-16 20:40 ` Thomas Petazzoni via buildroot
2025-04-16 20:49 ` Thomas Perale via buildroot
2025-04-18 10:39 ` Thomas Petazzoni via buildroot
2025-04-21 20:19 ` Thomas Perale via buildroot
2025-04-22 12:53 ` Thomas Petazzoni via buildroot
2025-04-22 14:00 ` Peter Korsgaard
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=87tt6o3oxx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@rnout.be \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.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