mirror of
https://github.com/commercialhaskell/stackage.git
synced 2026-01-27 06:31:56 +01:00
Mention Packdeps
This commit is contained in:
parent
51f13eb932
commit
26a075c4e4
@ -37,8 +37,19 @@ $ rm -f stack.yaml && stack init --resolver nightly --solver
|
|||||||
$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
|
$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
|
||||||
```
|
```
|
||||||
|
|
||||||
Or, alternatively, with `cabal` (may end up using older dependency
|
This approach works well, but has two limitations you should be aware
|
||||||
versions):
|
of:
|
||||||
|
|
||||||
|
* It won't notify you of restrictive upper bounds in your package if
|
||||||
|
Stackage has the same upper bounds. For that reason, we recommend
|
||||||
|
using [Packdeps](http://packdeps.haskellers.com/) (see "Following
|
||||||
|
dependency upgrades" below).
|
||||||
|
* If the latest Stackage Nightly is missing some of the latest
|
||||||
|
packages, your build above may succeed whereas the Travis job may
|
||||||
|
fail. Again: Packdeps will help you detect this situation.
|
||||||
|
|
||||||
|
Alternatively, you can build with `cabal`. Note that this may end up
|
||||||
|
using older dependency versions:
|
||||||
|
|
||||||
```
|
```
|
||||||
$ ghc --version # Should be the same as the latest nightly, it's in the title of https://www.stackage.org/nightly
|
$ ghc --version # Should be the same as the latest nightly, it's in the title of https://www.stackage.org/nightly
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user