on master help sign in
Better Stack instructions using tarball
commit51f13eb9329e58ca1ce10439e940fbfb3d3805ba authorMichael Snoyman <michael@snoyman.com> dateMon 27 Nov 2017, 09:09 (9 years ago) parentfcdf3fb
1 file changed+5−6
MAINTAINERS.md+5−6
MAINTAINERS.md+5−6
@@ -29,13 +29,12 @@ The CI job notably doesn't compile packages, run tests, build documentation, or
2929If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
3030
3131```
32−$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
33−```
34−
35−Or, if some dependencies haven't made it into Stackage Nightly yet:
36−
37−```
32+# Build from the tarball on Hackage to check for missing files
33+$ stack unpack yourpackage && cd yourpackage-*
34+# Generate a pristine stack.yaml, adding any missing extra-deps
3835$ rm -f stack.yaml && stack init --resolver nightly --solver
36+# Build, generate docs, test, and build benchmarks
37+$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
3938```
4039
4140Or, alternatively, with `cabal` (may end up using older dependency