This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 24 Jun, 2014 4 commits
  2. 09 Jun, 2014 1 commit
    • 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
  3. 23 May, 2014 2 commits
    • 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
    • Andres Löh's avatar
      Treat flags with much less priority. · 5e7c7f69
      Andres Löh authored
      This implements two changes:
      
      (1) Flag choices are deferred whenever possible.
      (2) If a package appears on both branches of a conditional, the
          unconstrained package is lifted out of the conditional.
      
      In combination, we're trying to achieve that the solver should pick
      a package before the flag, and thereby e.g. respect installed package
      versions.
      
      This is adequate in the common use case that flags are simply
      representing a disjunction, and should be rather weak.
      
      We'll have to see what happens in the few other situations where flags
      are really representing optional features. I'd expect, however, that
      in such situations there are targets in one branch, and not the other.
      Then the flag choice would still happen prior to the corresponding
      target.
      
      (cherry picked from commit 91abc4f9)
      5e7c7f69
  4. 20 May, 2014 2 commits
    • Andres Löh's avatar
      Fix flag goal generation (and hopefully #1855). · a57fe48d
      Andres Löh authored
      Package flags generate (Boolean) goals. Package flags can be dependent
      on one another, in situations such as this one:
      
        if flag(a)
          ...
        else
          if flag(b)
            ...
          else
            ...
      
      In such a scenario, it's important to record that flag b depends on flag
      a. This affects conflict set generation. If something fails due to the
      choice of flag b, we should not backjump beyond flag a.
      
      While the code handling the proper insertion of goals with their correct
      dependencies was always there, it was accidentally overridden by another
      piece of code that created flag goals (without dependencies) for all
      flags defined in a package. The reason I add flag goals separately is
      because not all paths in the decision tree may contain choices for all
      flags of a package. For example, if a is chosen to be True in the
      example above, b does not occur at all. But flag choices may still
      affect other things that aren't visible to the solver (directory
      choices, exposed modules, ...), so all flags declared should always be
      chosen explicitly. So we want to keep adding all flags declared in a
      package as dummies, but we have to make sure to do so *before* adding
      the actual dependency tree. This way, while traversing the dependency
      tree, the ones occurring in dependencies will be added again, overriding
      the dummies, rather than the other way round (which we used to have
      before, where the dummies were overwriting the more informative
      versions).
      
      (cherry picked from commit a51b8378)
      a57fe48d
    • Andres Löh's avatar
      Fix a flag-handling bug related to #1855. · 5b58dc88
      Andres Löh authored
      This was an innocent-looking but severe bug that was triggered for manual
      flags in certain circumstances: if both choices of a manual flag are
      already invalidated by other decisions, then the old code was removing
      the nodes underneath the flag completely. As a result, there's a node
      with no children rather than a node with two failure-children. The
      fail-nodes carry important information that is used to compute how far
      we can backtrack. If this information is removed, strange things happen.
      
      (cherry picked from commit 3e33a0f3)
      5b58dc88
  5. 19 May, 2014 1 commit
  6. 02 May, 2014 2 commits
  7. 18 Apr, 2014 2 commits
  8. 14 Apr, 2014 2 commits
  9. 13 Apr, 2014 1 commit
  10. 12 Apr, 2014 7 commits
  11. 11 Apr, 2014 1 commit
  12. 10 Apr, 2014 3 commits
  13. 09 Apr, 2014 1 commit
  14. 05 Apr, 2014 1 commit
    • barmston's avatar
      Don't freeze non-required installed packages · ea2651c4
      barmston authored
      An InstallPlan contains installed packages in the package database which are
      not required to satisfy the dependencies of the user targets. To prevent
      including them in the frozen set of constraints, `Freeze.planPackages` uses
      `D.C.PackageIndex.dependencyClosure` to try and take the transitive closure of
      the package dependencies.
      
      Whilst it is possible for `pruneInstallPlan` to fail, only valid
      `InstallPlan`s are passed to it. If a failure does occur, we error.
      ea2651c4
  15. 02 Apr, 2014 2 commits
    • barmston's avatar
      Frozen dependencies are printed on their own lines · 5b5f729a
      barmston authored
      A new pretty-print has been introduced `D.ParseUtils.commaNewLineListField`.
      It is similar to `D.ParseUtils.commaListField` but has each item on its own
      line.
      
      The constraints section of the package environment is pretty printed with
      `commaNewLineListField`.
      5b5f729a
    • Ian D. Bollinger's avatar
      Fix #1569. · 85fecab0
      Ian D. Bollinger authored
      * Change `guessPackageName` to translate arbitrary strings into valid
      package names.
      * Change type of `packageName` flag from String to PackageName and
      reject names that do not pass PackageName's corresponding parse
      function.
      85fecab0
  16. 30 Mar, 2014 2 commits
  17. 21 Mar, 2014 4 commits
  18. 19 Mar, 2014 1 commit
  19. 05 Mar, 2014 1 commit