1 |
On 10/01/2011 12:40 AM, Robin H. Johnson wrote: |
2 |
> diff --git a/pym/portage/const.py b/pym/portage/const.py |
3 |
> index 8b5f4ac..a42ebe8 100644 |
4 |
> --- a/pym/portage/const.py |
5 |
> +++ b/pym/portage/const.py |
6 |
> @@ -109,10 +109,12 @@ EAPI = 4 |
7 |
> |
8 |
> HASHING_BLOCKSIZE = 32768 |
9 |
> MANIFEST1_HASH_FUNCTIONS = ("MD5", "SHA256", "RMD160") |
10 |
> -MANIFEST2_HASH_FUNCTIONS = ("SHA1", "SHA256", "RMD160") |
11 |
> +MANIFEST2_HASH_FUNCTIONS = ("SHA256", "SHA512", "WHIRLPOOL") |
12 |
> +# FUTURE: Add SHA-3 when available; remove SHA256 after 2012/10/01 |
13 |
> |
14 |
> MANIFEST1_REQUIRED_HASH = "MD5" |
15 |
> -MANIFEST2_REQUIRED_HASH = "SHA1" |
16 |
> +MANIFEST2_REQUIRED_HASH = "SHA256" |
17 |
> +# FUTURE: Change to WHIRLPOOL after 2012/10/01 |
18 |
> |
19 |
> MANIFEST2_IDENTIFIERS = ("AUX", "MISC", "DIST", "EBUILD") |
20 |
> # =========================================================================== |
21 |
|
22 |
If we control these hashes via metadata/layout.conf, then we can toggle |
23 |
it atomically for all commiters. Otherwise, we'll have an annoying |
24 |
period of time where different committers are committing different sets |
25 |
of hashes, depending on their portage version. |
26 |
-- |
27 |
Thanks, |
28 |
Zac |