New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to uninstall stack #3563
Comments
Removing Sorry that stack or haskell didn't work out for you! Anything in particular amiss? Or just trying it out and deciding not to pursue further?
I do not see how this is sloppy, it is way more reliable to ship static binaries. |
Thank you for the quick feedback. Stack works just fine for me. I'm just having trouble on this machine right now. Regarding "sloppy": This was a reference to the function you called |
I'm glad :D Feel free to create more issues in the future if you encounter any difficulties or if there are features you'd like.
Oh, I see. I should have guessed by sloppy being in quotes. No worries! I think it being called sloppy isn't due to the static vs dynamic. Instead, it's just that it doesn't know how to install the dependencies. If you're having trouble with it on that machine, it's likely due to these dependencies. |
I cannot remove /usr/local/bin/stack , i get "permission denied". I am trying to change the permissions, but still it doesn't work. |
Just use |
I did what you say. However I can still using stack command and it looks like everything was fine |
@VALENTINAMOVILSANDOVAL, I could not follow your comment above. Are you saying that you have tried to uninstall Stack but Stack still seems to be present? If yes, what operating system are you using? |
Hi,
I installed stack from https://get.haskellstack.org/ and now I'd like to remove it from this computer.
I know it has files in ~/.stack and the binary in /usr/local/bin. As far as I can tell the installer used the "sloppy" method (on LInuxmint) and downloaded a static binary.
Does it reside in other locations? Is there a more canonical approach?
Best regards,
Matthias
The text was updated successfully, but these errors were encountered: