From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH v2] doc: ref_make_variables: document new CVE variables
Date: Mon, 10 Feb 2025 11:06:23 +0100 [thread overview]
Message-ID: <20250210100623.353373-1-rhi@pengutronix.de> (raw)
In-Reply-To: <Z6YyLVP-ulaWguZ1@pengutronix.de>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
v2:
* separate blocks for each variable
* mention <vendor>:<product> syntax and multiple values
---
doc/ref_make_variables.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst
index 358701aab9e2..bfd01098f517 100644
--- a/doc/ref_make_variables.rst
+++ b/doc/ref_make_variables.rst
@@ -256,6 +256,19 @@ Package Definition
UTF-8 files the encoding can be specified with ``encoding=<enc>``.
See the section :ref:`licensing_in_packages` for more information.
+``<PKG>_CVE_PRODUCT``
+ The product ID in the `CVE Database <https://www.cve.org>`__, used for
+ generating SBoM reports.
+ It can be of the form ``<vendor>:<product>`` and contain multiple values
+ separated by spaces if necessary.
+ If not set, it defaults to ``<PKG>``.
+
+``<PKG>_CVE_VERSION``
+ The version number in the `CVE Database <https://www.cve.org>`__, used for
+ generating SBoM reports.
+ If not set, it defaults to ``$(<PKG>_VERSION)``.
+
+
For most packages the variables described above are undefined by default.
However, for cross and host packages these variables default to the value
of the corresponding target package if it exists.
--
2.39.5
next prev parent reply other threads:[~2025-02-10 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:45 [ptxdist] [PATCH] " Roland Hieber
2025-02-07 16:17 ` Michael Olbrich
2025-02-10 10:06 ` Roland Hieber [this message]
2025-02-10 10:11 ` [ptxdist] [PATCH v3] " Roland Hieber
2025-02-17 7:24 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20250210100623.353373-1-rhi@pengutronix.de \
--to=rhi@pengutronix.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