From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe via buildroot <buildroot@buildroot.org>
Cc: Titouan Christophe <titouan.christophe@mind.be>,
Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH] package/rust: add CPE_ID_VENDOR
Date: Mon, 28 Jul 2025 22:45:22 +0200 [thread overview]
Message-ID: <20250728224522.359de135@windsurf> (raw)
In-Reply-To: <20250728102956.81525-1-titouan.christophe@mind.be>
Hello Titouan,
On Mon, 28 Jul 2025 12:29:56 +0200
Titouan Christophe via buildroot <buildroot@buildroot.org> wrote:
> This gives a proper cpe-id string to the Rust buildroot package
>
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
We typically want some kind of proof/evidence that this string is
correct, like:
package/python-future: add CPE identifier
The cpe:2.3:a:pythoncharmers:python-future:*:*:*:*:*:*:*:* is
valid for this package.
See https://nvd.nist.gov/products/cpe/detail/6E3F033B-5565-461B-8450-D23E68419313
> +RUST_CPE_ID_VENDOR = "rust-lang"
Doubles quotes around the variable value are not needed.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-07-28 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 10:29 [Buildroot] [PATCH] package/rust: add CPE_ID_VENDOR Titouan Christophe via buildroot
2025-07-28 20:45 ` Thomas Petazzoni via buildroot [this message]
2025-07-29 9:47 ` [Buildroot] [PATCH v2] " Titouan Christophe via buildroot
2025-07-29 12:20 ` Thomas Petazzoni via buildroot
2025-07-29 23:40 ` Julien Olivain via buildroot
2025-08-07 18:24 ` 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=20250728224522.359de135@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@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