cabal-rangefinder
cabal-rangefinder copied to clipboard
gelisam
A tool to fill in the version ranges in a cabal file.
Documented [here](http://blog.ezyang.com/2016/05/announcing-cabal-new-build-nix-style-local-builds/), `new-build` will eliminate a lot of waste by reusing already built configurations. We currently nuke the sandbox and rebuild everything for each step of the binary search, which...
The "base" package is determined by the version of GHC which is installed on the system, I can't just install every single version of the Haskell platform in order to...
Sometimes, the package compiles fine on a given version, but the tests don't run. Currently, we don't run the tests at all. We should. But since running the tests often...
https://hackage.haskell.org/package/tasty-golden
Instead of trying the full range for every dependency, we can restrict the range to look at (including upper bounds!) by starting from the information at the [Hackage Matrix Builder](http://matrix.hackage.haskell.org/)
I don't know what made me think that other versions of those packages could not be installed, but that's just not true. So, which packages should be pinned? Only base?...
Since we clear and recreate the sandbox every time, any source path added by `cabal sandbox add-source` is currently lost.
Instead of filling the screen with pages and pages output (to indicate that the program isn't stuck), maybe estimate how long it will take (measure the time of one compilation,...
Given the many new features I would like to add, the current minimalistic ``` usage: cabal-rangefinder ./my-package.cabal ``` won't cut it. Here is the new, expanded API I am thinking...