QuickCheck versions and 'cabal install'

[Stephen Blackheath [to cabal-devel]]

All,

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-4.2.0.1 requires QuickCheck ==1.2.0.0
however
QuickCheck-1.2.0.0 was excluded because QuickCheck-2.1.0.1 was selected
instead
QuickCheck-1.2.0.0 was excluded because test-framework-quickcheck2-0.2.2
requires QuickCheck >=2.1.0.0
QuickCheck-1.2.0.0 was excluded because ProjectX-0.1 requires QuickCheck
>=2.1

It isn't practical to fix this properly - That would require lots of
work upgrading quickcheck on all dependent packages.  (Crypto-4.2.0.1 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)?


Steve