@@ -42,26 +42,11 @@ of:
42* It won't notify you of restrictive upper bounds in your package if
42* It won't notify you of restrictive upper bounds in your package if
43 Stackage has the same upper bounds. For that reason, we recommend
43 Stackage has the same upper bounds. For that reason, we recommend
44 using [Packdeps](http://packdeps.haskellers.com/) (see "Following
44 using [Packdeps](http://packdeps.haskellers.com/) (see "Following
45− dependency upgrades" below).
45+ dependency upgrades" below). You can also run `cabal outdated`.
46* If the latest Stackage Nightly is missing some of the latest
46* If the latest Stackage Nightly is missing some of the latest
47 packages, your build above may succeed whereas the Travis job may
47 packages, your build above may succeed whereas the Travis job may
48 fail. Again: Packdeps will help you detect this situation.
48 fail. Again: Packdeps will help you detect this situation.
50−Alternatively, you can build with `cabal`. Note that this may end up
51−using older dependency versions:
54−$ ghc --version # Should be the same as the latest nightly, it's in the title of https://www.stackage.org/nightly
58−$ cabal sandbox init # Should give "Creating a new sandbox" and not "Using an existing sandbox".
59−$ cabal install --enable-tests --enable-benchmarks --dry-run | grep latest # Should give no results
60−$ cabal install --enable-tests --enable-benchmarks --allow-newer
65## Github and Notifications
50## Github and Notifications
67Stackage uses Github notifications to reduce overhead of contacting individual
52Stackage uses Github notifications to reduce overhead of contacting individual