-
Notifications
You must be signed in to change notification settings - Fork 799
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
stackage check does not check for the cabal-install version #35
Comments
I don't believe As far as the error message, it's actually implying the correct thing. The requirement is that the library version it be built against be greater than 1.16. There were certain sandboxing bugs in the 1.14 version of the library that cause problems for Stackage in certain use cases (such as shared libraries), which is why we have the requirement for 1.16. Technically, the means we require |
I am quite certain that the version of the cabal binary is checked in build and matters also for check, as shown by the following session:
|
Sorry, I wasn't clear. It is checking the cabal binary, but checking which version of the Cabal library it was compiled against. The fact that |
OK, updates pushed, what do you think? |
Judging from looking at the code I’d say that this is fine. |
Hi,
it seems that both "stackage check" and "stackage build" require a specific version of the cabal binary, but only "stackage build" checks this.
Also, the error message should be clearer and indicate that it is the binary cabal in the path whose version is insufficient (and not the locally installed Cabal library, or the Cabal library in the build plan).
Thanks,
Joachim
The text was updated successfully, but these errors were encountered: