This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 05 Sep, 2016 1 commit
  2. 21 Aug, 2016 1 commit
    • Edward Z. Yang's avatar
      Solve for, build, and add to path build-tools dependencies. · c0a48602
      Edward Z. Yang authored
      
      
      This fixes #220: new-build now builds, installs and adds executables to
      PATH automatically if they show up in 'build-tools'.  However, there is
      still more that could be done: the new behavior only applies to a
      specific list of 'build-tools' (alex, happy, etc) which Cabal recognizes
      out of the box.  The plan is to introduce a new 'tool-depends' field to
      allow dependencies on other executables as well.
      
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      c0a48602
  3. 30 Jul, 2016 1 commit
    • kristenk's avatar
      Avoid filtering the solver log before 'showMessages'. · f2d02983
      kristenk authored
      Previously, the solver filtered out redundant backjumping messages twice, once
      in 'Log.logToProgress' and again in 'Message.showMessages. However,
      'showMessages' relied on the backjumping messages to determine where to insert
      messages about missing packages. This led to missing "unknown package" messages
      (part of issue #3617).
      
      This commit removes the filtering in 'logToProgress', because it was redundant.
      f2d02983
  4. 16 Jul, 2016 1 commit
  5. 04 Jul, 2016 1 commit
  6. 03 Jul, 2016 3 commits
  7. 27 Jun, 2016 4 commits
  8. 07 May, 2016 1 commit
  9. 26 Apr, 2016 1 commit
  10. 24 Apr, 2016 1 commit
  11. 23 Apr, 2016 1 commit
  12. 22 Apr, 2016 3 commits
    • Andres Löh's avatar
      Allow to test error messages in the solver tests. · 268edadb
      Andres Löh authored
      Added this so that we can verify the unknown package error.
      268edadb
    • Andres Löh's avatar
      Add the current goal to the initial conflict set while backjumping. · 018e9365
      Andres Löh authored
      This is relevant for unknown packages. Without the current
      goal in the initial conflict set, the unknown package itself
      does not end up in its own conflict set.
      
      But we want it to, if only to make sure that the error slicing
      machinery keeps the message about the unknown goal around.
      
      It is also the correct thing to do. The initial conflict set
      corresponds to a virtual "avoid" choice underneath the package
      goal. That choice corresponds to avoiding assigning any proper
      value to the goal at all, which might be possible if the goal
      was not needed. The conflict set for this "avoid" goal is always
      between the current package and its immediate goal reason.
      
      I have added comments to the code explaining this as well.
      018e9365
    • Andres Löh's avatar
      Add two more solver test cases. · 162d2580
      Andres Löh authored
      162d2580
  13. 21 Apr, 2016 3 commits
    • kristenk's avatar
      Use larger conflict set when solver chooses wrong version for package in link group · 7f480594
      kristenk authored and Edsko de Vries's avatar Edsko de Vries committed
      This commit replaces a call to 'lgBlame' with a call to 'lgConflictSet'.
      'lgConflictSet' adds the members of the link group to the conflict set. The
      other members are required, for example, when a linked package's version doesn't
      match a constraint, and the solver must try other versions for the linked-to
      package.
      
      All tests now pass.
      7f480594
    • Edsko de Vries's avatar
      Declare indepGoals3 as passing. · 440033d6
      Edsko de Vries authored
      440033d6
    • Edsko de Vries's avatar
      Use empty POption for unknown packages · 5a4149f4
      Edsko de Vries authored
      and fix the error message in showMessages; this keeps the construction of
      conflict sets uniform.
      
      This still isn't quite right though. If we remove B from db21 as well, we don't see a line "unknown package B" appearing in the log. I have no idea why.
      
      Also, @kosmikus says:
      
      > ok, so first problem: we still need to add C to the conflict set
      > one way to do this now is to change the "initial" conflict set in the backjump calls to be the node + the goal reason again
      > I was assuming that the initial set is only ever added to an existing conflict set that we already have
      > but this is now no longer true
      
      I have no idea what that means :)
      5a4149f4
  14. 20 Apr, 2016 1 commit
  15. 18 Apr, 2016 11 commits
  16. 17 Apr, 2016 3 commits
  17. 13 Apr, 2016 1 commit
  18. 03 Apr, 2016 1 commit
    • kristenk's avatar
      Simplify representation of test suites in the solver DSL · 931b5a19
      kristenk authored
      This commit removes the 'ExTest' constructor from 'ExampleDependency'.
      Test dependencies are now represented using the same
      'ExampleDependency' constructors as library dependencies.  The only
      difference between dependencies of different components is that they
      are placed under different keys in 'D.C.ComponentDeps.ComponentDeps'.
      931b5a19
  19. 31 Mar, 2016 1 commit