-
Notifications
You must be signed in to change notification settings - Fork 71
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
Support allow-newer
in constraint-set
#670
Comments
I have now more evidence why a
So, adding a constraint set that requires a In the wild I experienced that adding a constraint set for
This strengthens the case for the OP, a local |
Initial discussion in a thread starting here: haskell-hvr/regex-tdfa#54 (comment)
I am trying to solve the following problem:
constraint-set
to test forbytestring-0.12
for some newer GHCs.allow-newer: bytestring
as some of my dependencies do not allowbytestring-0.12
yet.xor
) will fail to configure on older GHCs if they are bound to the installedbytestring
.xor
) will also fail to build if their upper bound is loosened.For example, looking at the following CI configuration:
allow-newer: bytestring
, on GHC 7.6xor
fails to build: https://github.com/haskell-hvr/http-io-streams/actions/runs/5597341206/jobs/10235561064?pr=12#step:17:197bytestring
, on GHC 7.6xor
fails to configure: https://github.com/haskell-hvr/http-io-streams/actions/runs/5600301654/jobs/10242494046?pr=12#step:15:27The principled solution would be to have a
allow-newer
that is scoped by aconstraint-set
rather than action globally viaraw-project
.The text was updated successfully, but these errors were encountered: