2db87333d7
Using stack's script command meant that the scripts needed to be compatible, and regularly tested, with a hledger release in stackage, rather than the latest hledger source. This created hassles for maintainers, contributors and sometimes for users. To simplify things overall, we now require script users to check out the hledger source tree and run the scripts (or, bin/compile.sh) from there once so they compile themselves. Some notes on alternative setups are included (in one of the scripts, and referenced by the others). This ensures that users and our CI tests are building scripts the same way. Current stack does not allow a stack options line to be used with the "stack ghc" command, unfortunately, so instead we are using env's -S flag, which hopefully has sufficiently wide support by now, and putting all arguments in the shebang line. This method will probably require complete explicit --package options, unlike "stack script", so more testing and tweaking is expected. Probably we're going to end up with some long shebang lines. This isn't pretty but seems like a possible way to keep things manageable.
13 lines
643 B
Plaintext
13 lines
643 B
Plaintext
# Functional tests for the add-on scripts in this directory.
|
|
|
|
# Check that they all (or at least these ones) still compile with this version of hledger.
|
|
# stdout and exit code are ignored for cleaner failure output.
|
|
# $ ./compile.sh >/dev/null
|
|
$ ./hledger-balance-as-budget.hs >/dev/null || true
|
|
$ ./hledger-check-fancyassertions.hs >/dev/null || true
|
|
$ ./hledger-check-tagfiles.hs >/dev/null || true
|
|
$ ./hledger-combine-balances.hs >/dev/null || true
|
|
$ ./hledger-print-location.hs >/dev/null || true
|
|
$ ./hledger-smooth.hs >/dev/null || true
|
|
$ ./hledger-swap-dates.hs >/dev/null || true
|