Skip to content

Commit 73605d2

Browse files
committed
Update installation instructions
1 parent f6b699c commit 73605d2

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

doc/install_and_upgrade.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ NOTE: These executables have been built and tested on a Windows 7, 8.1, and 10 6
1818

1919
We generally test on the current version of OS X, but stack is known to work on Mavericks as well, and may also work on older versions (YMMV).
2020

21-
**Note**: due to [GHC bug 10322](https://ghc.haskell.org/trac/ghc/ticket/10322), building `stack` from source fails with GHC 7.10.1. This bug is fixed in GHC 7.10.2, and GHC 7.8.4 works as well.
22-
2321
## Ubuntu
2422

2523
*note*: for 32-bit, use the [generic Linux option](#linux)
@@ -175,4 +173,4 @@ There are essentially three different approaches to upgrade:
175173

176174
* If you're using a package manager (e.g., the Ubuntu debs listed above) and are happy with sticking with the officially released binaries, simply follow your normal package manager strategies for upgrading (e.g. `apt-get update && apt-get upgrade`).
177175
* If you're not using a package manager but want to stick with the official binaries (such as on Windows or Mac), you'll need to manually follow the steps above to download the newest binaries from the release page and replace the old binary.
178-
* The `stack` tool itself ships with an `upgrade` command, which will build `stack` from source and install it to the default install path (see the previous section). You can use `stack upgrade` to get the latest official release, and `stack upgrade --git` to install from Git and leave on the bleeding edge. If you follow this, make sure that this directory is on your `PATH` and takes precedence over the system installed `stack`. For more information, see [this discussion](https://github.com/commercialhaskell/stack/issues/237#issuecomment-126793301).
176+
* The `stack` tool itself ships with an `upgrade` command, which will build `stack` from source and install it to the default install path (see the previous section). You can use `stack upgrade` to get the latest official release, and `stack upgrade --git` to install from Git and leave on the bleeding edge. If you follow this, make sure that this directory is on your `PATH` and takes precedence over the system installed `stack`. For more information, see [this discussion](https://github.com/commercialhaskell/stack/issues/237#issuecomment-126793301).

0 commit comments

Comments
 (0)