This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 09 Mar, 2012 1 commit
  2. 17 Feb, 2012 1 commit
  3. 19 Feb, 2012 1 commit
  4. 22 Feb, 2012 1 commit
  5. 17 Feb, 2012 1 commit
  6. 16 Feb, 2012 2 commits
  7. 04 Feb, 2012 1 commit
  8. 13 Feb, 2012 1 commit
    • Andres Löh's avatar
      make test and bench available as user constraints · 88cc7ccb
      Andres Löh authored
      Saying
      
        cabal install foo --enable-tests
      
      is now equivalent to saying
      
        cabal install foo --constraint="foo test"
      
      The constraint syntax in addition allows to enable tests and benchmarks
      for packages that are further down in the dependency chain.
      88cc7ccb
  9. 12 Feb, 2012 2 commits
  10. 11 Feb, 2012 2 commits
  11. 08 Feb, 2012 1 commit
  12. 07 Feb, 2012 3 commits
    • ttuegel's avatar
    • ttuegel's avatar
      Update types in modular dependency solver to compile with new test/benchmark... · 2c603664
      ttuegel authored
      Update types in modular dependency solver to compile with new test/benchmark dependency constraints.
      2c603664
    • ttuegel's avatar
      Handle test and benchmark dependencies through the resolver properly. · 2978ef8b
      ttuegel authored
      Previously, test and benchmark dependencies were handled by editing the
      package description to include or exclude those stanzas before running
      the dependency resolver. Test and benchmark dependencies could only be
      installed for source packages because no package description is available
      for named packages before dependency resolution.
      
      Now, test and benchmark stanzas are enabled or disabled through constraints
      passed to the dependency resolver. This way, we can install dependencies for
      the test suites of target packages without propagating '--enable-tests'
      through the entire dependency tree; i.e., tests and benchmarks, when enabled,
      are built only for target packages. Later, this will allow us to
      automatically run test suites and, e.g., install only upon their success.
      2978ef8b
  13. 10 Jan, 2012 2 commits
  14. 12 Dec, 2011 2 commits
  15. 09 Jan, 2012 1 commit
  16. 01 Jan, 2012 1 commit
  17. 16 Dec, 2011 1 commit
  18. 17 Nov, 2011 1 commit
  19. 16 Nov, 2011 2 commits
  20. 11 Nov, 2011 1 commit
  21. 07 Nov, 2011 3 commits
  22. 04 Nov, 2011 1 commit
  23. 03 Nov, 2011 1 commit
  24. 29 Oct, 2011 5 commits
  25. 28 Oct, 2011 2 commits