On Tue, 2016-12-20 at 23:30 +0000, Pádraig Brady wrote: > On 20/12/16 22:28, Christopher wrote: > > > > What's with the new sources format? > > The old format, I could do `md5sum -c sources` > > Why not make the new format with SHA512 follow the same pattern, so > > I could do: `shasum -c sources` or `sha512sum -c sources`? > > > > Is there any standard command-line tool to parse this new format, > > or do I just gotta grep/awk/bash my way through it? > > As far as I can see it's using the BSD tagged format, It is. This is a decision we made when moving to sha512, because we wanted the file to contain the used hash function. (for the future, when we invariably move again to a new hash function) We were starting to talk about our own format, then someone (I think it might have been Peter?) told me about the BSD tagged format, and we just went with that. > which the coreutils sha512sum command can parse. > I.E. the following format is supported since v8.20 (2012-10-23) > > SHA512 (filename) = ... Not only can it parse it, it can also generate it: $ sha512sum --tag some-file SHA512 (some-file) = ... -- Mathieu _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
