Please can you make SHA256SUM.md more machine/script friendly.
At present, for example, it is not possible to use it in scripts with pipefail enabled beause sha256sum -c --ignore-missing --strict SHA256SUM.md returns multiple values for the same file and sha256sum will exit !=0 if any check is !=OK.
This means you have to do a somewhat messy workaround of removing pipefail and doing sha256sum -c --ignore-missing --strict SHA256SUM.md | grep -F OK and checking the exit code from grep.
Maybe (as a minimum) you could start issuing something like SHA256SUM_CURRENT which contains only the data for the current release ? And issue it in machine readable form without markdown etc.
Alternatively, if you want to keep the historical data in one place, maybe don't issue it in markdown format, but json format. Then at least people can parse it with jq to get the data for the release they want.
Please can you make SHA256SUM.md more machine/script friendly.
At present, for example, it is not possible to use it in scripts with
pipefailenabled beausesha256sum -c --ignore-missing --strict SHA256SUM.mdreturns multiple values for the same file andsha256sumwill exit !=0 if any check is !=OK.This means you have to do a somewhat messy workaround of removing
pipefailand doingsha256sum -c --ignore-missing --strict SHA256SUM.md | grep -F OKand checking the exit code from grep.Maybe (as a minimum) you could start issuing something like
SHA256SUM_CURRENTwhich contains only the data for the current release ? And issue it in machine readable form without markdown etc.Alternatively, if you want to keep the historical data in one place, maybe don't issue it in markdown format, but json format. Then at least people can parse it with
jqto get the data for the release they want.