From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] glep-0075: Update for reference implementation
Date: Fri, 25 Oct 2019 08:26:31 +0200 [thread overview]
Message-ID: <9d1d89c2166d3199463faa72dcc2bc64a5c4d0e1.camel@gentoo.org> (raw)
In-Reply-To: <w6gpnil6fpx.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On Thu, 2019-10-24 at 22:39 +0200, Ulrich Mueller wrote:
> > > > > > On Thu, 24 Oct 2019, Michał Górny wrote:
> > +in 2⁴ = 16 directories), and each of this directories would have
>
> s/this/these/ (This was there before, but can be corrected while at it.)
>
> > +The implementations are only required to support cutoffs being multiples
>
> s/The implementations/Implementations/
Both fixed in place. Since they're grammar fixes, I suppose there's
no need to send v2 over it.
>
> > +and maintaining mirrors via ``emirrordist``. The implementation
> > +supports both listed layouts, with all hash functions supported
> > +by Portage and cutoffs being multiples of 4.
>
> In the rationale section, one reason given for the choice of the hash
> algorithm (BLAKE2B) was to "avoid code duplication". Isn't that argument
> moot, if all hashes supported by Portage are implemented? (Or in other
> words, couldn't a faster hash function like MD5 be used?)
That's a very Portage-centric thinking. Technically, today's PM needs
only to be implement SHA512 and BLAKE2B. The former is legacy,
so in the future we will probably throw it away and either leave BLAKE2B
only, or add another new hash. In either case, BLAKE2B is the most
future-proof choice today.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2019-10-25 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:50 [gentoo-dev] [PATCH] glep-0075: Update for reference implementation Michał Górny
2019-10-24 20:39 ` Ulrich Mueller
2019-10-24 21:00 ` Hanno Böck
2019-10-25 6:26 ` Michał Górny [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d1d89c2166d3199463faa72dcc2bc64a5c4d0e1.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox