The *sum tools will test all lines in a checksum file and will return 0 if any match or 1 if none match.
md5sum --quiet -c xxx.asc < xxx.tar.gz sha1sum --quiet -c xxx.asc < xxx.tar.gz sha256sum --quiet -c xxx.asc < xxx.tar.gz where xxx.asc is ecb9ac329728d0b2b947d4b2fba85b53b00dbf81737fc6db7e5e343025f98536 xxx.tar.gz 28f1a190d4b4d03a36744e9ba8518c8ca42e9276 xxx.tar.gz 5feb02a70a357cbbca1458498d5ed655 xxx.tar.gz will all return 0. sha512sum --quiet -c xxx.asc < xxx.tar.gz will return 1 because there's no sha512 line in the text file. On Sun, Dec 22, 2013 at 9:27 AM, Matthew Jordan <[email protected]> wrote: > > On Sun, Dec 22, 2013 at 7:31 AM, Ben Langfeld <[email protected]> wrote: > >> If everything went in one checksum file, how would one (or shasum) tell >> each of the checksums apart? >> >> I'll submit a patch to mkrelease for the extra files. >> >> > I was thinking a JSON blob, but I'm perfectly happy with multiple files as > well. > > -- > Matthew Jordan > Digium, Inc. | Engineering Manager > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
