aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormerakor <cem@ckyln.com>2021-03-24 04:59:31 +0000
committermerakor <cem@ckyln.com>2021-03-24 04:59:31 +0000
commite816cab6f5f4eaa0e63f7f0ce751cde0f96b5a4b (patch)
tree66c861c255c377a6b3198c0d4516bcd8a068f869
parent6bf775511658a8d1db300b97a155c3bbfe3f3bb1 (diff)
downloadcpt-e816cab6f5f4eaa0e63f7f0ce751cde0f96b5a4b.tar.gz
docs: update
FossilOrigin-Name: 51658a4ad9ab409e8cc776d2640cb2eb6da420ea0791f071142afb0a588b67d2
-rw-r--r--src/cpt-lib.in11
1 files changed, 5 insertions, 6 deletions
diff --git a/src/cpt-lib.in b/src/cpt-lib.in
index d9a5808..c6d3866 100644
--- a/src/cpt-lib.in
+++ b/src/cpt-lib.in
@@ -470,12 +470,11 @@ decompress() {
}
sh256() {
- # This is a sha256sum function for outputting a standard
- # hash digest. sha256 on BSD systems require an '-r' flag
- # for outputting the same way with sha256sum, and still,
- # it outputs a single space between the hash and the file
- # whereas sha256sum outputs double spaces. It fallbacks to
- # openssl, but that is rarely ever needed.
+ # This is a sha256sum function for outputting a standard hash digest. sha256
+ # on BSD systems require an '-r' flag for outputting the same way with
+ # sha256sum, and still, it outputs a single space between the hash and the
+ # file whereas sha256sum outputs double spaces. It fallbacks to openssl, but
+ # that is rarely ever needed.
{ sha256sum "$1" 2>/dev/null ||
sha256 -r "$1" 2>/dev/null ||
openssl dgst -r -sha256 "$1" ||