id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,difficulty,ghcversion,platform
719,tool support for checking if a package works with a range of versions,duncan,,"[http://www.haskell.org/pipermail/libraries/2010-July/013970.html 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
make too)
}}}

Others responded that they would also like to do the same thing locally, even though the range of versions they have locally may be limited.

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.",enhancement,new,normal,cabal-install-0.16,cabal-install tool,,normal,,,,easy (<4 hours),,