(Imported from Trac #719, reported by @dcoutts on 2010-07-28)
Doaitse reports that he would like:
since I do not have a wide variety of Haskell installations and
package versions on my machine, it would be very nice if the
hackage server could test a package against the extremes of the
indicated dependency ranges before installing. This would have
prevented the mistake I made (and which undoubtedly others will
So one simple approach would be a flag to indicate a preference that the earliest version of a package (or all packages?) be used rather than the latest version. This might be integrated into a "cabal disttest" feature that makes a tarball and builds from the tarball.
The same approach could be taken for hackage build bots.
(Imported comment by @benmachine on 2010-07-28)
See also #661
(Imported comment by @kosmikus on 2010-12-08)
The modular solver can in principle be adapted easily to produce several solutions to the dependency resolution problem. But there can be far too many in practice so that trying them all probably is not feasible. Using the earliest versions by default is simple enough, though.