-
Notifications
You must be signed in to change notification settings - Fork 843
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
Comments
Coming from #494. I had a quick look at the code and I had the impression that the In any case I'd like to solve this issue because that's a blocker for me. |
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 |
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. |
Based on that answer, the easiest solution to this is to provide a |
I'm thinking of bundling this with |
Considering how slow/buggy older versions can be...
The text was updated successfully, but these errors were encountered: