Re: Have makesum target display hashes in common format

2021-09-06 Thread Marc Espie
On Mon, Sep 06, 2021 at 02:01:08PM +0100, Stuart Henderson wrote: > On 2021/09/06 14:48, Marc Espie wrote: > > On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote: > > > > > > Kurt Mosiejczuk writes: > > > > > > > On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote: > > > > >

Re: Have makesum target display hashes in common format

2021-09-06 Thread Stuart Henderson
On 2021/09/06 14:48, Marc Espie wrote: > On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote: > > > > Kurt Mosiejczuk 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?)! > > > > >

Re: Have makesum target display hashes in common format

2021-09-06 Thread Marc Espie
On Fri, Sep 03, 2021 at 01:34:57PM -0600, Aaron Bieber wrote: > > Kurt Mosiejczuk 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

Re: Have makesum target display hashes in common format

2021-09-03 Thread Stuart Henderson
On 2021/09/03 15:20, Kurt Mosiejczuk wrote: > On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote: > > > Put it into a `show-checksums' target so the regular `makesum' does not > > get slowed down on already big/slow ports? > > I don't understand this suggestion. makesum only gets run

Re: Have makesum target display hashes in common format

2021-09-03 Thread Aaron Bieber
Kurt Mosiejczuk 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

Re: Have makesum target display hashes in common format

2021-09-03 Thread Kurt Mosiejczuk
On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote: > Put it into a `show-checksums' target so the regular `makesum' does not > get slowed down on already big/slow ports? I don't understand this suggestion. makesum only gets run when one updates a port. The existing output it fairly

Re: Have makesum target display hashes in common format

2021-09-03 Thread Kurt Mosiejczuk
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

Re: Have makesum target display hashes in common format

2021-09-03 Thread Klemens Nanni
On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote: > > Kurt Mosiejczuk 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

Re: Have makesum target display hashes in common format

2021-09-03 Thread Aaron Bieber
Kurt Mosiejczuk 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

Have makesum target display hashes in common format

2021-09-03 Thread Kurt Mosiejczuk
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