1 |
The comment is based upon the wrong assumption that the world is |
2 |
Portage-centric. We are keeping the manifest-hashes in layout.conf |
3 |
indefinitely, and we will most likely take BLAKE2 instead of SHA3. |
4 |
--- |
5 |
pym/portage/const.py | 23 ----------------------- |
6 |
1 file changed, 23 deletions(-) |
7 |
|
8 |
diff --git a/pym/portage/const.py b/pym/portage/const.py |
9 |
index cbd2b6042..11e94b0a2 100644 |
10 |
--- a/pym/portage/const.py |
11 |
+++ b/pym/portage/const.py |
12 |
@@ -207,29 +207,6 @@ EAPI = 6 |
13 |
HASHING_BLOCKSIZE = 32768 |
14 |
MANIFEST1_HASH_FUNCTIONS = ("MD5", "SHA256", "RMD160") |
15 |
|
16 |
-# Past events: |
17 |
-# |
18 |
-# 20120704 - After WHIRLPOOL is supported in stable portage: |
19 |
-# - Set manifest-hashes in gentoo-x86/metadata/layout.conf as follows: |
20 |
-# manifest-hashes = SHA256 SHA512 WHIRLPOOL |
21 |
-# - Add SHA512 and WHIRLPOOL to MANIFEST2_HASH_DEFAULTS. |
22 |
-# - Remove SHA1 and RMD160 from MANIFEST2_HASH_*. |
23 |
-# |
24 |
-# Future events: |
25 |
-# |
26 |
-# After WHIRLPOOL is supported in stable portage for at least 1 year: |
27 |
-# - Change MANIFEST2_REQUIRED_HASH to WHIRLPOOL. |
28 |
-# - Remove SHA256 from MANIFEST2_HASH_*. |
29 |
-# - Set manifest-hashes in gentoo-x86/metadata/layout.conf as follows: |
30 |
-# manifest-hashes = SHA512 WHIRLPOOL |
31 |
-# |
32 |
-# After SHA-3 is supported in stable portage: |
33 |
-# - Set manifest-hashes in gentoo-x86/metadata/layout.conf as follows: |
34 |
-# manifest-hashes = SHA3 SHA512 WHIRLPOOL |
35 |
-# |
36 |
-# After layout.conf settings correspond to defaults in stable portage: |
37 |
-# - Remove redundant settings from gentoo-x86/metadata/layout.conf. |
38 |
- |
39 |
MANIFEST2_HASH_FUNCTIONS = ("SHA256", "SHA512", "WHIRLPOOL", |
40 |
"BLAKE2B", "BLAKE2S", "SHA3_256", "SHA3_512", |
41 |
"STREEBOG256", "STREEBOG512") |
42 |
-- |
43 |
2.15.0 |