On 2021/09/06 14:48, Marc Espie wrote: > On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote: > > > > Kurt Mosiejczuk <k...@cranky.work> writes: > > > > > On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote: > > > > > >> 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 > > > > > > Does go actually publish base64 SHA256 hashes for their modules? > > > If not, it's not the size of the output that makes that useless. > > > > They do, but checking by hand is redundant as the checks are all built > > into the tooling. > > > > For example: https://sum.golang.org/lookup/suah.dev/ogvt@v1.1.0 > > > > (the h1:blablabl stuff is an encoded sha256 hash) > > > > > > > >> Maybe it can be conditional.. somehow? > > > > > > Why? How often do you do a "make makesum"? I do it like once per port > > > update and verify my distfiles. > > > > > > > It seems like I do it quite often. Though maybe it just stands out > > because the Go lists are always sofaking big! > > > > > --Kurt > > I think it would be more sense to append it to a file, having the name > be /dev/null by default, for those few individuals who actually need this >
I really would like it to not calculate at all if it's not needed, some of the distfiles are huge and sha256 and md5 is definitely non-trivial, especially over NFS
