Replace the informational hash name section with a formal specification
of allowed hash algorithms. The original reasoning for leaving them implementation-defined was poor. After all, not a single new hash
was added since the initial version of the GLEP. At the same time,
ensuring consistent support for at least a minimal set of hash
algorithms is crucial to interoperability. Given that the effort needed
to update the GLEP is relatively small, it is better to require all
algorithms to be formally listed than to have to track all
implementations for new hashes and hope for consistency.
Signed-off-by: Michał Górny <
mgorny@gentoo.org>
---
glep-0074.rst | 125 +++++++++++++++++++++++++++++++-------------------
1 file changed, 77 insertions(+), 48 deletions(-)
diff --git a/glep-0074.rst b/glep-0074.rst
index 8cec618..33f6f80 100644
--- a/glep-0074.rst
+++ b/glep-0074.rst
@@ -6,7 +6,7 @@ Author: Michał Górny <
mgorny@gentoo.org>,
Ulrich Müller <
ulm@gentoo.org>
Type: Standards Track
Status: Final
-Version: 1.2
+Version: 1.3
Created: 2017-10-21
Last-Modified: 2022-09-11
Post-History: 2017-10-26, 2017-11-16, 2018-02-08, 2022-09-08, 2022-09-11
@@ -26,6 +26,9 @@ efficient and provide means of backwards compatibility.
Changes
=======
+v1.3
+ Formally specified the current set of hash algorithms supported.
+
v1.2
Specified the newline convention used for Manifests.
@@ -364,27 +367,50 @@ up to and including the *original* directory. Note that those
sub-Manifests can use different filenames than ``Manifest``.
-Checksum algorithms (informational)
------------------------------------
-
-Thi