(Imported from Trac #661, reported by @benmachine on 2010-04-19)
When developing a package, you want to specify as wide a range of build-depends as possible, but it's often quite tedious to keep checking if your latest development effort hasn't made your package incompatible with some ancient version of a library you use.
In view of this I think it would be helpful to have an option that asks cabal configure to pick the oldest possible version of each dependency, so you could quickly and easily ensure that at least the two endpoints are covered.
(Imported comment by @dcoutts on 2010-04-19)
Doable by adjusting the soft preferences in the cabal-install resolver.
(Imported comment by @benmachine on 2010-04-20)
See also #719 - in fact this might well be considered a duplicate of that one.
This has been implemented in pull-request #1309.
Duplicate of #2228.