You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/install_and_upgrade.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -295,10 +295,18 @@ For more information and other shells, see [the shell auto-completion page](shel
295
295
296
296
## Upgrade
297
297
298
-
There are essentially three different approaches to upgrade:
298
+
There are essentially four different approaches to upgrade:
299
299
300
-
* 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 live 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).
300
+
* The `stack` tool itself ships with an `upgrade` command, which download a`stack`binary or build it from source and install it to the default install path (e.g. `~/.local/bin` or `%APPDATA%\local\bin`; see the [Path](#Path) section above). You can use `stack upgrade` to get the latest official release, and `stack upgrade --git` to install from Git and live on the bleeding edge. Make sure the default install directory is on your `PATH` and takes precedence over the system installed `stack`, or copy `stack` from that directory to the system location afterward. For more information, see [this discussion](https://github.com/commercialhaskell/stack/issues/237#issuecomment-126793301).
301
301
302
-
* 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`).
302
+
* If you're using a package manager and are happy with sticking with the officially released binaries from the distribution (which may the lag behind latest version of Stack significantly), simply follow your normal package manager strategies for upgrading (e.g. `apt-get update && apt-get upgrade`).
303
303
304
-
* 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.
304
+
* The get.haskellstack.org script supports the `-f` argument to over-write the current stack executable. For example:
305
+
306
+
curl -sSL https://get.haskellstack.org/ | sh -s - -f
307
+
308
+
or:
309
+
310
+
wget -qO- https://get.haskellstack.org/ | sh -s - -f
311
+
312
+
* Manually follow the steps above to download the newest binaries from the release page and replace the old binary.
0 commit comments