Improved PATH-aware behavior for stack upgrade
#3232
Closed
Comments
snoyberg
added a commit
that referenced
this issue
Jun 27, 2017
snoyberg
added a commit
that referenced
this issue
Jul 13, 2017
borsboom
added a commit
that referenced
this issue
Jul 19, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem: users will often run the install script and end up with
stack
in/usr/local/bin
, and when they runstack upgrade
, are surprised that the nextstack
call still uses the old version. To mitigate this, @borsboom and I propose:stack upgrade
continues to copy the executable to~/.local/bin
as it has until nowstack
executable to the location of the current executables.source file path
todest file path
sudo
to perform the copy (and explain that it may fail due to OS specific things)sudo cp ...
, and potentially similar commands withsu
.Presumably we won't even bother trying this on Windows.
The text was updated successfully, but these errors were encountered: