This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 28 Jun, 2014 3 commits
  2. 27 Jun, 2014 1 commit
  3. 26 Jun, 2014 7 commits
  4. 25 Jun, 2014 5 commits
  5. 24 Jun, 2014 12 commits
  6. 21 Jun, 2014 1 commit
  7. 19 Jun, 2014 2 commits
  8. 16 Jun, 2014 2 commits
  9. 12 Jun, 2014 1 commit
  10. 11 Jun, 2014 1 commit
  11. 10 Jun, 2014 1 commit
  12. 09 Jun, 2014 3 commits
    • Herbert Valerio Riedel's avatar
      Allow template-haskell to be upgradable again · ffd67e5e
      Herbert Valerio Riedel authored
      This partly reverts 65e9b88b
      which marked `template-haskell` non-upgradable. However, since are now
      able to fix-up wrong .cabal meta-data on Hackage, previous `template-haskell`
      releases have been augmented by proper version bounds so that it's now
      safe again to let the Cabal solver handle reinstalling `template-haskell`
      
      See also #1811, #667, #1761, and #1444
      
      (cherry picked from commit 65ae95c1 / #1934)
      ffd67e5e
    • Herbert Valerio Riedel's avatar
      Merge pull request #1934 from hvr/pr-unwire-th · ae093bd6
      Herbert Valerio Riedel authored
      Allow template-haskell to be upgradable again
      ae093bd6
    • Herbert Valerio Riedel's avatar
      Allow template-haskell to be upgradable again · 65ae95c1
      Herbert Valerio Riedel authored
      This partly reverts 65e9b88b
      which marked `template-haskell` non-upgradable. However, since are now
      able to fix-up wrong .cabal meta-data on Hackage, previous `template-haskell`
      releases have been augmented by proper version bounds so that it's now
      safe again to let the Cabal solver handle reinstalling `template-haskell`
      
      See also #1811, #667, #1761, and #1444
      65ae95c1
  13. 07 Jun, 2014 1 commit
    • Andres Löh's avatar
      Treat all flags of a package as interdependent. · 3f777568
      Andres Löh authored
      There was an open bug that could cause conflict sets to be
      computed incorrectly if flags were involved in the conflict
      set. Incorrectly computed conflict sets can lead to the solver not
      finding solutions even though they actually exist.
      
      Because I decided that computing flag dependencies correctly is tricky
      and probably not worth the effort, we're now treating all flags (of a
      package) as mutually dependent. This means that if any flag choice ends
      up in a conflict set, then it's as if all flag choices (of the same
      package) are in that conflict set. This is potentially slower for
      packages having many flags, but it should at least be correct, because
      it's conservative.
      3f777568