cabal install doesn't trip the -fnew-bytestring-builder flag :''''( #190

Closed
cartazio opened this Issue Mar 12, 2014 · 1 comment

Comments

Projects
None yet
2 participants
carter ~ » cabal install aeson --dry
Resolving dependencies...
In order, the following would be installed (use -v for more details):
bytestring-0.10.2.0 (latest: 0.10.4.0)
dlist-0.6.0.1
syb-0.4.1
text-1.0.0.1 (latest: 1.1.0.1)
hashable-1.2.1.0
scientific-0.2.0.2
attoparsec-0.11.2.1
unordered-containers-0.2.3.3

but i'm on 7.8RC with the newer text and bytestring.... it should detect that!

I realize this is per se a cabal-install issue not an aeson one, but it will impact folks none the less. I hit a similar issue with one of snoyman's packages recently.

I feel like there must be a bug in the cabal install flag explorer part of the solver if this sorts of things are so easy to trip up

Owner

bos commented Mar 12, 2014

This is a duplicate of #177.

bos closed this Mar 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment