aboutsummaryrefslogtreecommitdiff
path: root/check/bin.sh
Commit message (Collapse)AuthorAgeFilesLines
* Use "shell" not "sh" consistentlyTom Ryder2017-10-311-2/+2
| | | | | I'm going to pretend this is a crucially important production fix, in order to try out the "hotfix" part of the "Git flow" workflow.
* Use shell name not command in check/lint messagesTom Ryder2017-10-311-3/+3
| | | | This is a little bit clearer and nicer to read, I think.
* Add conditional Bash `check-bin`, `lint-bin`Tom Ryder2017-10-311-0/+11
| | | | | | Both blocks are analogues of the POSIX checks, but are wrapped in a conditional so that bash(1) doesn't become a hard dependency of the default `make install` target.
* Correct misleading output for `lint-bin`Tom Ryder2017-10-311-1/+1
| | | | | We haven't checked all of the shell scripts, just the POSIX sh ones, which at present, is all but one of them; han(1df).
* Adjust `check-bin`, `lint-bin` for built scriptsTom Ryder2017-10-311-1/+1
| | | | | | | | | | | | | | | | Make the `$(BINS)` target a prerequisite of `check-bin` so that all of the scripts with a #!/bin/sh shebang are built, and then check them all by iterating through a glob (and hence an order according to LC_COLLATE) and stripping the `.sh` suffix to find the name of the matching shebanged script. Leverage `shellcheck`'s support of multiple check arguments to build an argument list of the binscripts first before passing all of those to a single call, simply for speed. We don't have anything in this target to test the scripts of any other type, such as the `.awk` or `.sed` scripts. `gawk` has a `--lint` mode that might apply.
* More sh flexibility (check/lint scripts)Tom Ryder2017-04-051-0/+4