On 11 February 2012 18:03, Antoine Latter
I'm using a development cut of cabal install from a few weeks ago, so this may not be relevant anymore (I'll upgrade soon to try the changes to --enable-tests and install soon), but I found this behavior odd:
When using 'cabal(-dev) install --only-dependecies --solver=modular --upgrade-dependencies' to test my package with new dependencies, I am then told I need to use the flag '--force-reinstalls'.
Shouldn't this be implied by '--upgrade-dependencies'?
We've not entirely decided what to do with the reinstall check. My preference for the behaviour is that it should check if any packages will be broken by the reinstall (not including the ones being installed themselves). I think this should do the right thing in most cases. Opinions welcome. Duncan