4 Commits (1a9f531c79f8a043db6f151c5393f23aa5675800)

Author	SHA1	Message	Date
Quentin Gliech	d4c4798a25	Use interpreter from $PATH instead of absolute paths in various scripts using /usr/bin/env (#9689) ... On NixOS, `bash` isn't under `/bin/bash` but rather in some directory in `$PATH`. Locally, I've been patching those scripts to make them work. `/usr/bin/env` seems to be the only [portable way](https://unix.stackexchange.com/questions/29608/why-is-it-better-to-use-usr-bin-env-name-instead-of-path-to-name-as-my) to use binaries from the PATH as interpreters. Signed-off-by: Quentin Gliech <quentingliech@gmail.com>	2021-03-25 16:53:54 +00:00
Andrew Morgan	22db45bd4d	Prevent the config-lint script erroring out on any sample_config changes (#9562) ... I noticed that I'd occasionally have `scripts-dev/lint.sh` fail when messing about with config options in my PR. The script calls `scripts-dev/config-lint.sh`, which attempts some validation on the sample config. It does this by using `sed` to edit the sample_config, and then seeing if the file changed using `git diff`. The problem is: if you changed the sample_config as part of your commit, this script will error regardless. This PR attempts to change the check so that existing, unstaged changes to the sample_config will not cause the script to report an invalid file.	2021-03-09 11:11:42 +00:00
Patrick Cloke	ba547ec3a9	Use BSD-compatible in-place editing for sed. (#6887)	2020-02-12 07:02:19 -05:00
Andrew Morgan	409c62b27b	Add config linting script that checks for bool casing (#6203) ... Add a linting script that enforces all boolean values in the default config be lowercase. This has annoyed me for a while so I decided to fix it.	2019-10-23 13:22:54 +01:00