The issue has originarily reported as pyenv/pyenv#902.
Unlike sha256sum of GNU coreutils, BusyBox one doesn't print '*'
and prints extra whitespaces, when computing digest from stdin.
sha256sum (GNU coreutils 8.26)
```
% cat /sbin/init | sha256sum -b
ef753e9504ada221155b86e7e6b7b4ff2499d64e27bcd959f0542bcac589feb1 *-
```
sha256sum (BusyBox v1.26.2)
```
/ # cat /sbin/init | sha256sum -b
4cd6d1a4028772fabc9166bb52b5826aec4e91874c107fce33dc515c04cb754f -
```
I also confirmed that md5sum behaves just similarly.
- Only call `openssl version` once;
- Make the check work with future version of LibreSSL after 2.2.7. This
assumes that Apple might keep updating LibreSSL shipping with macOS,
but that they will never provide header files.
* standard_build invoke configure and make. It not invoke `make install`.
* standard_install invoke only `make install`.
* Added backword compatibility function for above separation.
* Added new function for bundled_gems support named standard_install_with_bundled_gems.
Bats doesn't support both suite-wide setup (in helper) *and* file-wide
setup. Which means the existance of any file-level setup() function
overwrites any setup() function from test_helper. This can be confusing,
and (IMO) easier to simply avoid the overwriting and remove any
_implied_ suite-wide setup function from test_helper.
This turns out to not be so bad for the recently added setup function,
because the only test files that actually need aria2c removed from PATH
are those that actually invoke curl. These can be found because they are
the only test files that stub curl; half of which already had
file-specific setup() functions. So the only ones which need a
file-local setup() function added were: checksum.bats and mirror.bats
Along these lines, rbenv.bats and hooks.bats were removing aria2c from
PATH but don't actually need to. (curl isn't stubbed in these tests so
the existance of aria2c wouldn't affect the tests)
Lastly, fixed a tab/spaces whitespace mixup that was introduced by:
750c086d11
