Commit e52e23f0 authored Apr 08, 2026 by Samuel Dionne-Riel

doc/meta: Fix documentation for `edition` CPE field

The field could have been simply removed from the list, as it is not
used, but it should be present in that form at least for *some
undefined* length of time to present as a correction for anyone using
the `edition` field mistakenly.

My claim comes from the literal source listed in the next paragraph
(NISTIR 7695), the first few words of `5.3.3.6` are:

> The edition attribute is considered deprecated

Thus we consider it deprecated.

Furthermore the section documents that it should be using the value
`ANY`. It could be considered debatable as `NA` should be used “when
there is no legal or meaningful value for that attribute, or when
that attribute is not used as part of the description”... But the spec
states that `ANY` should be used, so we state `ANY` should be used.

parent 9ac62ecd

doc/stdenv/meta.chapter.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -292,7 +292,7 @@ Some of them are as follows:
		* product - name of the package
		* version - version of the package
		* update - name of the latest update, can be a patch version for semantically versioned packages
		* edition - any additional specification about the version
		* edition - deprecated and should be set to `*`

		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).