Closed andrewthad closed 4 years ago
btw, such a undiscriminated use of --allow-newer
is something we should really deprecate in cabal; that's just asking for trouble... :-/
Here's a more principled use of --allow-newer
which is more surgical rather than the naive "ignore all constraints on bytestring regardless of any invariants" sledge-hammer:
--allow-newer="cassava-0.5.2.0:bytestring"
--constraint="cassava -bytestring--lt-0_10_4"
--constraint="bytestring >= 0.10.4"
Hello @hvr thanks for the tip, is there any way to specify an array for allow-newer
in stack.yaml
?
I tried this
allow-newer:
- cassava-0.5.2.0:bytestring
but Stack complains:
Error in $['allow-newer']: failed to parse field 'allow-newer': expected Bool, but encountered Array
This command sequences fails:
I get several errors which all stem from