Better Stack instructions using tarball

This commit is contained in:
Michael Snoyman 2017-11-27 09:09:22 +02:00
parent fcdf3fb77b
commit 51f13eb932
No known key found for this signature in database
GPG Key ID: A048E8C057E86876

View File

@ -29,13 +29,12 @@ The CI job notably doesn't compile packages, run tests, build documentation, or
If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
```
$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
```
Or, if some dependencies haven't made it into Stackage Nightly yet:
```
# Build from the tarball on Hackage to check for missing files
$ stack unpack yourpackage && cd yourpackage-*
# Generate a pristine stack.yaml, adding any missing extra-deps
$ rm -f stack.yaml && stack init --resolver nightly --solver
# Build, generate docs, test, and build benchmarks
$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
```
Or, alternatively, with `cabal` (may end up using older dependency