This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 29 Jul, 2014 3 commits
  2. 21 Jul, 2014 1 commit
    • Isamu Mogi's avatar
      Read installed package info file as UTF-8 · 44a261d4
      Isamu Mogi authored
      Currently installed package info file is written in UTF-8. So UTF-8
      should be used explicitly or it can cause "invalid byte sequence"
      error if system encoding is incompatible to UTF-8.
      44a261d4
  3. 25 Jun, 2014 2 commits
  4. 24 Jun, 2014 7 commits
  5. 28 May, 2014 1 commit
  6. 23 May, 2014 1 commit
    • Andres Löh's avatar
      Configurable strong/weak flags. · f950e8d7
      Andres Löh authored
      This adds a mechanism in the modular solver to store whether a flag
      is "strong" or "weak". A weak flag is deferred during solving, a strong
      flag is not.
      
      By default, flags are now weak unless they're manual. This is a change
      in behaviour, but I think it's probably the better default, because many
      automatic flags are used to figure out what's on the system rather than
      to impose hard constraints.
      
      There's a new flag --strong-flags that restores the old behaviour. I do
      not think such a global flag is particularly useful, but it may be
      of interest to compare build plans between the new and old behaviour.
      
      With these preparations, it's easy to make the distinction between
      strong and weak flags more sophisticated. We can either add more
      heuristics as to when flags should be treated as strong or weak, or we
      can add syntax to .cabal files that allows package authors to specify
      explicitly how they intend a flag to behave.
      
      This is related to various cabal-install issues, e.g. #1831, #1864,
      and #1877.
      
      (cherry picked from commit 3dcddea4)
      
      Conflicts:
      	cabal-install/Distribution/Client/Dependency.hs
      f950e8d7
  7. 19 May, 2014 1 commit
    • Andres Löh's avatar
      Configurable strong/weak flags. · 3dcddea4
      Andres Löh authored
      This adds a mechanism in the modular solver to store whether a flag
      is "strong" or "weak". A weak flag is deferred during solving, a strong
      flag is not.
      
      By default, flags are now weak unless they're manual. This is a change
      in behaviour, but I think it's probably the better default, because many
      automatic flags are used to figure out what's on the system rather than
      to impose hard constraints.
      
      There's a new flag --strong-flags that restores the old behaviour. I do
      not think such a global flag is particularly useful, but it may be
      of interest to compare build plans between the new and old behaviour.
      
      With these preparations, it's easy to make the distinction between
      strong and weak flags more sophisticated. We can either add more
      heuristics as to when flags should be treated as strong or weak, or we
      can add syntax to .cabal files that allows package authors to specify
      explicitly how they intend a flag to behave.
      
      This is related to various cabal-install issues, e.g. #1831, #1864,
      and #1877.
      3dcddea4
  8. 11 May, 2014 1 commit
  9. 14 Apr, 2014 1 commit
  10. 10 Apr, 2014 1 commit
  11. 21 Mar, 2014 1 commit
  12. 19 Dec, 2013 2 commits
  13. 17 Dec, 2013 2 commits
  14. 06 Dec, 2013 2 commits
  15. 05 Dec, 2013 3 commits
    • Mikhail Glushenkov's avatar
      Whitespace, formatting. · 270e771d
      Mikhail Glushenkov authored
      270e771d
    • Mikhail Glushenkov's avatar
    • Mikhail Glushenkov's avatar
      Solver support for '--allow-newer'. · d5ea0dfc
      Mikhail Glushenkov authored
      Implemented by going through all packages in the 'depResolverSourcePkgIndex' and
      applying 'relaxUpperBound' to the dependencies listed in 'build-depends'.
      
      Known issue:
      'build-depends: a < 3 && >= 2; if (someFlag): build-depends: a >= 5 && < 6'
      gets converted to
      'build-depends: >= 2; if (someFlag): build-depends: a >= 5'
      (4 is now allowed where it previously wasn't).
      
      Example:
      
          $ cabal install --dry-run ./tst
          Resolving dependencies...
          In order, the following would be installed (use -v for more details):
          array-0.3.0.3 (latest: 0.5.0.0)
          tst-0.1.0.0 (latest: 0.1.1)
      
          $ cabal install --dry-run --allow-newer=array ./tst
          Resolving dependencies...
          In order, the following would be installed (use -v for more details):
          tst-0.1.0.0 (latest: 0.1.1)
      d5ea0dfc
  16. 04 Dec, 2013 1 commit
    • Mikhail Glushenkov's avatar
      Refactoring: change the return type of 'InstallPlan.ready'. · 2a75a448
      Mikhail Glushenkov authored
      Introduce a new type 'ReadyPackage' to represent packages that have all
      dependencies already installed. Make 'InstallPlan.ready' return '[ReadyPackage]'
      instead of '[(ConfiguredPackage, InstalledPackageInfo)]'.
      
      Also fix a bug where 'cabal configure' didn't pass '--dependency' options to
      'setup configure'.
      2a75a448
  17. 02 Dec, 2013 1 commit
  18. 22 Nov, 2013 1 commit
  19. 31 Oct, 2013 4 commits
  20. 29 Oct, 2013 1 commit
  21. 26 Oct, 2013 3 commits