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

Consider allowing newer versions of Cabal library #174

Closed
snoyberg opened this issue Jun 3, 2015 · 5 comments
Closed

Consider allowing newer versions of Cabal library #174

snoyberg opened this issue Jun 3, 2015 · 5 comments
Assignees
Milestone

Comments

@snoyberg
Copy link
Contributor

@snoyberg snoyberg commented Jun 3, 2015

Considering how slow/buggy older versions can be...

@snoyberg snoyberg self-assigned this Jun 3, 2015
@snoyberg snoyberg added this to the Third release milestone Jun 3, 2015
@snoyberg snoyberg added this to the Later improvements milestone Jun 9, 2015
@snoyberg snoyberg removed this from the First stable release (0.1.0.0?) milestone Jun 9, 2015
@snoyberg snoyberg removed their assignment Jun 16, 2015
@etorreborre
Copy link

@etorreborre etorreborre commented Jul 3, 2015

Coming from #494.

I had a quick look at the code and I had the impression that the getCabalPkgVer function could try to get it version number from the EnvOverride but I don't know the code base enough to really tell.

In any case I'd like to solve this issue because that's a blocker for me.

Loading

@snoyberg
Copy link
Contributor Author

@snoyberg snoyberg commented Jul 3, 2015

The way is works now is that stack will always use the version of Cabal in the global package database. So one option for a short-term hack is to do something like cabal install --global Cabal. I think a better long term solution is having some kind of extra package database available which contains the Cabal library, and then provide a stack command to install new versions of the Cabal library. We could also have some kind of a field in stack.yaml which specifies which version of Cabal is necessary, and automatically install it if missing.

Loading

@etorreborre
Copy link

@etorreborre etorreborre commented Jul 4, 2015

That works for me in the short term, thanks. In the long run it would be nice to be able to specify the Cabal version in the stack.yaml file.

Loading

@snoyberg
Copy link
Contributor Author

@snoyberg snoyberg commented Jul 7, 2015

Based on that answer, the easiest solution to this is to provide a stack upgrade-cabal command or similar that installs a new version of Cabal to the global database.

Loading

@snoyberg snoyberg self-assigned this Jul 31, 2015
@snoyberg
Copy link
Contributor Author

@snoyberg snoyberg commented Jul 31, 2015

I'm thinking of bundling this with stack setup, as a flag --upgrade-cabal, and having it simply automate downloading the most recent Cabal library and doing a global install of it.

Loading

@snoyberg snoyberg closed this in df9a810 Jul 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants