This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 06 Jun, 2018 1 commit
  2. 13 May, 2018 2 commits
  3. 09 May, 2018 4 commits
    • kristenk's avatar
      Solver: Enforce dependencies on libraries (fixes #779). · 6efb5e23
      kristenk authored
      This commit generalizes the fix for issue #4781
      (e86f8389) by tracking dependencies on
      components instead of dependencies on executables.  That means that the solver
      always checks whether a package contains a library before using it to satisfy a
      build-depends dependency.  If a version of a package doesn't contain a library,
      the solver can try other versions.  Associating each dependency with a component
      also moves towards the design for component-based dependency solving described
      in issue #4087.
      6efb5e23
    • kristenk's avatar
      Solver DSL: Support packages without libraries. · 1743a4d8
      kristenk authored
      The solver DSL previously always added a default library component.
      1743a4d8
    • kristenk's avatar
      Solver DSL: Support benchmarks, internal libraries, and foreign libraries. · 1bc42a89
      kristenk authored
      This change allows the solver quickcheck tests to test all types of components.
      Previously, the tests generated the components in the solver DSL, but the code
      that converted the packages to GenericPackageDescriptions removed some of the
      components, i.e., it filtered out benchmarks and foreign libraries and merged
      internal libraries with the main library.
      1bc42a89
    • kristenk's avatar
      Add CABAL_DIR environment variable for specifying the cabal directory. · a343dee1
      kristenk authored
      CABAL_DIR can be used to run integration tests independently on Windows,
      since setting HOME doesn't affect the location of the APPDATA directory.
      a343dee1
  4. 08 May, 2018 1 commit
    • quasicomputational's avatar
      Allow ** wildcards in globs. · 5e83ef26
      quasicomputational authored
      These are inspired by a plan described in a comment in #2522, and only
      implement a quite limited form of recursive matching: only a single **
      wildcard is accepted, it must be the final directory, and, if a **
      wildcard is present, the file name must include a wildcard.
      
      Or-patterns are not implemented, for simplicity.
      
      Closes #3178, #2030.
      5e83ef26
  5. 27 Apr, 2018 1 commit
  6. 26 Apr, 2018 1 commit
  7. 19 Apr, 2018 2 commits
  8. 16 Apr, 2018 2 commits
  9. 10 Apr, 2018 1 commit
  10. 05 Apr, 2018 1 commit
  11. 28 Mar, 2018 3 commits
  12. 27 Mar, 2018 5 commits
  13. 26 Mar, 2018 1 commit
    • alexbiehl's avatar
      Haddock: Generate haddock for components · 4466310e
      alexbiehl authored
      Currently settings `documentation: true` enables documentation
      generation via haddock for your whole package, including tests and benchmarks.
      However, there are additional flags to control generation of
      documentation for this "second class" documentation targets, which are
      currently not honored at the cabal-install side of things. Namely,
      `tests`, `benchmarks`, `executables`, etc. provided under the
      `haddock` section in your `$CABAL_HOME/config`.
      
      This patch adds a more sensible approach to documentation generation
      via haddock. Also enabling `new-haddock` to generate documentation for
      single components instead whole packages.
      
      The behaviour works like this:
      
          - Setting `documentation: true` or passing
            `--enable-documentation` to cabal-install enable documentation
            for any component in the build plan honoring the respective
            flags for tests, benchmarks, exes, foreignlibs, etc.
      
          - Invoking new-haddock with a target selector will make sure
            the respective flags for "second class" doc targets are set
            correctly. E.g.
      
            $ new-haddock tests
      
            Will generate documentation for the testsuite of your package
            event if you have `tests: false` in your haddock section.
      4466310e
  14. 25 Mar, 2018 1 commit
  15. 22 Mar, 2018 1 commit
  16. 15 Mar, 2018 1 commit
  17. 13 Mar, 2018 2 commits
  18. 11 Mar, 2018 3 commits
  19. 10 Mar, 2018 3 commits
  20. 09 Mar, 2018 1 commit
  21. 08 Mar, 2018 1 commit
  22. 06 Mar, 2018 2 commits