MAINTAINERS.md: Remove outdated cabal instructions, I'm not sure how to do this now

This commit is contained in:
Adam Bergmark 2021-03-21 14:12:03 +01:00
parent 5c0aa93473
commit 43fc7c2e88

View File

@ -42,26 +42,11 @@ of:
* It won't notify you of restrictive upper bounds in your package if * It won't notify you of restrictive upper bounds in your package if
Stackage has the same upper bounds. For that reason, we recommend Stackage has the same upper bounds. For that reason, we recommend
using [Packdeps](http://packdeps.haskellers.com/) (see "Following using [Packdeps](http://packdeps.haskellers.com/) (see "Following
dependency upgrades" below). dependency upgrades" below). You can also run `cabal outdated`.
* If the latest Stackage Nightly is missing some of the latest * If the latest Stackage Nightly is missing some of the latest
packages, your build above may succeed whereas the Travis job may packages, your build above may succeed whereas the Travis job may
fail. Again: Packdeps will help you detect this situation. 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
$ cabal update
$ cabal get PACKAGE
$ cd PACKAGE-*
$ cabal sandbox init # Should give "Creating a new sandbox" and not "Using an existing sandbox".
$ cabal install --enable-tests --enable-benchmarks --dry-run | grep latest # Should give no results
$ cabal install --enable-tests --enable-benchmarks --allow-newer
$ cabal test
$ cabal haddock
```
## Github and Notifications ## Github and Notifications
Stackage uses Github notifications to reduce overhead of contacting individual Stackage uses Github notifications to reduce overhead of contacting individual