From 9ac62ecd610df82312d4c396de11b446f94ce249 Mon Sep 17 00:00:00 2001 From: Samuel Dionne-Riel Date: Wed, 8 Apr 2026 14:09:28 -0400 Subject: [PATCH] doc/meta: Reword *logical values* for CPEs The original wording missed the *not meaningful* nuance, and adding an `or` clause within the sentence would have made it hard to understand. Instead, it is now split into a list, and ordered in the same order as found in `5.3.1` in NISTIR 7695. The logical name used by the specification (ANY/NA) was also added. --- doc/stdenv/meta.chapter.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/stdenv/meta.chapter.md b/doc/stdenv/meta.chapter.md index 1e1e190b3eda..285211a401da 100644 --- a/doc/stdenv/meta.chapter.md +++ b/doc/stdenv/meta.chapter.md @@ -296,7 +296,10 @@ Some of them are as follows: You can find information about all of these attributes in the [official specification](https://csrc.nist.gov/projects/security-content-automation-protocol/specifications/cpe/naming) (heading 5.3.3, pages 11-13). -Any fields that don't have a value are set to either `-` if the value is not available or `*` when the field can match any value. +Any fields that don't have a value are set to either: + +* `*` (ANY) when the field can match any value +* `-` (NA) when the value is not meaningful or not used in the description For example, for glibc 2.40.1 CPE would be `cpe:2.3:a:gnu:glibc:2.40:1:*:*:*:*:*:*`.