QuickCheck versions and 'cabal install'

Stephen Blackheath [to cabal-devel] rubbernecking.trumpet.stephen at blacksapphire.com
Wed Jun 10 08:36:22 EDT 2009


I'm getting a lot of this kind of problem now that a new major version
of QuickCheck has come out...

blackh at amentet:~/src/projectx$ cabal install
Resolving dependencies...
cabal: dependencies conflict: Crypto- requires QuickCheck ==
QuickCheck- was excluded because QuickCheck- was selected
QuickCheck- was excluded because test-framework-quickcheck2-0.2.2
requires QuickCheck >=
QuickCheck- was excluded because ProjectX-0.1 requires QuickCheck

It isn't practical to fix this properly - That would require lots of
work upgrading quickcheck on all dependent packages.  (Crypto- is
my hacked version of Crypto-4.2.0 with a closed upper version limit to
prevent it forcing QuickCheck-2.* which won't compile.)

Is there a better solution to this problem?

Should a package maintainer have the right to choose an old version of
QuickCheck, or should cabal's policy force all package maintainers to
upgrade (preferably all on the same day)?


More information about the cabal-devel mailing list