This project is mirrored from https://github.com/haskell/Cabal.
Pull mirroring updated .
- 17 Jul, 2014 3 commits
-
-
Daniel Trstenjak authored
Pretty print the fields of flags nested.
-
Daniel Trstenjak authored
-
Daniel Trstenjak authored
Remove the special casing for strings starting with a newline. Handle all newlines in strings the same way, by replacing them with a '.'.
-
- 15 Jul, 2014 4 commits
-
-
Mikhail Glushenkov authored
Fixes #1994 (hopefully).
-
Mikhail Glushenkov authored
Small cleanup
-
Mikhail Glushenkov authored
Included targets in cabal's bash-completion.
-
Mikhail Glushenkov authored
Self-constraint not included in frozen constraints
-
- 11 Jul, 2014 2 commits
-
-
barmston authored
-
Mikhail Glushenkov authored
-
- 06 Jul, 2014 2 commits
-
-
Mikhail Glushenkov authored
Use SVG for the Travis badge in the README
-
MaxGabriel authored
-
- 02 Jul, 2014 1 commit
-
-
Thomas Miedema authored
-
- 29 Jun, 2014 2 commits
-
-
Mikhail Glushenkov authored
Refactor exec command to use the ConfiguredProgram abstraction
-
barmston authored
-
- 28 Jun, 2014 7 commits
- 27 Jun, 2014 1 commit
-
-
Herbert Valerio Riedel authored
See also ghc/ghc@1c0b5fdc for more details
-
- 26 Jun, 2014 7 commits
-
-
tibbe authored
A duplicate definition was somehow added while merging and was causing build failures.
-
tibbe authored
-
tibbe authored
-
tibbe authored
Post cabal-install-1.20.0.3 release. Conflicts: Cabal/Cabal.cabal Cabal/Makefile cabal-install/cabal-install.cabal
-
tibbe authored
-
tibbe authored
Document 'cabal test --show-details=streaming' (#1964)
-
Miëtek Bak authored
-
- 25 Jun, 2014 5 commits
-
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
- 24 Jun, 2014 6 commits
-
-
Mikhail Glushenkov authored
Make it more clear why that call is necessary.
-
(cherry picked from commit 5c46e785)
-
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. (cherry picked from commit 3f777568)
-
(cherry picked from commit f00dc68e)