Re: Have makesum target display hashes in common format

On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
>
> Kurt Mosiejczuk <kurt@cranky.work> writes:
>
> > Whenever I update a port or create a new one, to verify the hashes I have
> > to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
> > has, but we use base64 format and everywhere else (that I've interacted with)
> > uses hexadecimal format.
> >
> > This diff makes the makesum target spit out hexadecimal formatted MD5 and
> > SHA256 hashes for each distfile. I included md5 because, sadly, a number of
> > projects still only provide an MD5 hash for verification.
> >
> > I've tested this with ports with both a single distfile and multiple
> > distfiles.
>
> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
>
> net/go-ipfs for example, the output is useless because it's so big :D
>
> Maybe it can be conditional.. somehow?

Put it into a `show-checksums' target so the regular `makesum' does not
get slowed down on already big/slow ports?