-
Notifications
You must be signed in to change notification settings - Fork 696
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
configure ignores --constraint flag #1150
Comments
I just verified that this works correctly with the old, topdown, solver. |
There's something I don't understand about the way cabal works here. As you can see from your log output, what actually happens is that the solver fails. However, So there are two points to investigate here:
|
Oh, perhaps I should add that as far as I can see this isn't a HEAD regression. I don't have your use case, but if you specify a clearly unsolvable constraint (such as "base == 1.0.0.0"), then you get similar behaviour with both solvers, already in 0.14.0. |
I am still seeing behavior like this in very new cabal-installs:
As you can see, I've specified a constraint (
|
Hm, issue #385 also looks relevant. Perhaps this was a conscious design choice? If so, put me down as requesting a feature that reports a little bit about what happened when the solver failed but configure succeeded anyway. It's a very confusing outcome. |
configure seems to ignore the
--contraint
flag. For example, here I'm specifying a specific version of hashable, but configures picks another one:The text was updated successfully, but these errors were encountered: