4 ms·
Got it. Thanks. Re --check, I suppose the way to do that would be to download the file to disk, which --check requires as fair as I can tell. So I could downlo
by gavinuhma 4y ago
Got it. Thanks.
Re --check, I suppose the way to do that would be to download the file to disk, which --check requires as fair as I can tell. So I could download the file to disk, --check, and then remove it. I think most of these installs scripts are trying not to leave any artifacts around from install, other than the resulting binary.
- dundarious 4y agoYou only need to create a temp file for the checksum file, not the downloaded contents. In the below example, no file exists on disk with the contents of `$s`. > $ s='1<space><space>2' > $ printf %s\\n "$s" | shasum -a 256 > tmp.sum > $ printf %s\\n "$s" | shasum --check tmp.sum > -: OK So you can just `printf '%s<space><space>-\n' "$c" > tmp.sum` and check with `printf %s\\n "$s" | shasum --check --status tmp.sum || { echo "checksum failed" > &2 ; exit 1 ; }` Having to create temp files is a wrinkle (could probably avoid it by using process substitution if you want to give up on POSIX sh), but so is writing bash scripts in general.
- gavinuhma 4y agoSolid! I couldn’t figure this out which I why I stopped using “—-check”. I’ll take a look
- gavinuhma 4y agoPr for that https://github.com/gavinuhma/checksum.sh/pull/4 https://github.com/gavinuhma/checksum.sh/pull/4 I ended up trying with process substitution so no tmp file. It works. Trying to decide if it’s more difficult to read