Skip to content
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

Bootstrap install of cabal-install should go into a common path, such as /usr/local/bin #2230

Open
bitemyapp opened this issue Nov 17, 2014 · 5 comments

Comments

@bitemyapp
Copy link
Contributor

https://gist.github.com/grownseed/4fd2e91eca829cc039de

GHC does this. Cabal should too, the inconsistency is pointless.

@23Skidoo
Copy link
Member

Note that you can use ./bootstrap.sh --global.

@bitemyapp
Copy link
Contributor Author

@23Skidoo users won't know about that. We should change the default. This is all about the default-path friction and what end-users are going to encounter.

@23Skidoo
Copy link
Member

I think bootstrap.sh always worked like that, so there's the issue of backwards compat. I guess we could add a Makefile that would just call ./bootstrap.sh --global for compatibility with GHC.

@bitemyapp
Copy link
Contributor Author

That's satisfactory for my purposes. Want me to PR it?

Edit: I will need to verify that "global" here doesn't mean cabal install --global, because if it does, that is also not terribly kosher. The point is to get the binary in a location that everybody will have in their path.

@23Skidoo
Copy link
Member

Sure, that'd be nice.

@ttuegel ttuegel added this to the cabal-install-1.24 milestone Apr 24, 2015
@23Skidoo 23Skidoo modified the milestones: cabal-install 1.24, cabal-install 1.26 Feb 21, 2016
@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants