mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] doc: ref_make_variables: document new CVE variables
Date: Fri, 7 Feb 2025 17:17:49 +0100	[thread overview]
Message-ID: <Z6YyLVP-ulaWguZ1@pengutronix.de> (raw)
In-Reply-To: <20250207134524.1990695-1-rhi@pengutronix.de>

On Fri, Feb 07, 2025 at 02:45:24PM +0100, Roland Hieber wrote:
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
>  doc/ref_make_variables.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/doc/ref_make_variables.rst b/doc/ref_make_variables.rst
> index 358701aab9e2..1c2f24b0db4d 100644
> --- a/doc/ref_make_variables.rst
> +++ b/doc/ref_make_variables.rst
> @@ -256,6 +256,12 @@ 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``, ``<PKG>_CVE_VERSION``
> +  The product ID and the version number used in the `CVE Database
> +  <https://www.cve.org>`__, used for generating SBoM reports.
> +  These variables only need to be set if their values differ from ``<PKG>`` and
> +  ``$(<PKG>_VERSION)`` respectively.

<PKG>_CVE_PRODUCT can be <vendor>:<product> if necessary, and it can be a
list if multiple vendor/product combinations are needed. I think that
should be documented as well :-)...

Michael

> +
>  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
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-02-07 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 13:45 Roland Hieber
2025-02-07 16:17 ` Michael Olbrich [this message]
2025-02-10 10:06   ` [ptxdist] [PATCH v2] " Roland Hieber
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=Z6YyLVP-ulaWguZ1@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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