Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
optionally select the oldest available dependencies rather than the newest #653
(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.