This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 02 Jun, 2018 1 commit
    • quasicomputational's avatar
      Be more efficient about globbing · 950f6d1a
      quasicomputational authored
      Before, we were walking the directory tree recursively
      unconditionally. Now we check if the pattern is recursive before doing
      that, and also only check the directory's full listing if a glob
      pattern is involved at all, so literal patterns are more efficient.
      950f6d1a
  2. 29 May, 2018 1 commit
  3. 25 May, 2018 10 commits
  4. 19 May, 2018 1 commit
    • quasicomputational's avatar
      Don't break when data-dir is null. · d0c3defe
      quasicomputational authored
      PR #5284 changed things around, and now matchDirFileGlob will break if
      it's passed a null directory, which happens to be the default value
      for data-dir. Its call sites have been fixed to check for this and to
      substitute '.' for an empty path, which is the desired behaviour; in
      addition, matchDirFileGlob itself will now warn about this if it's
      detected, so that new broken call sites can't sneak in.
      
      Fixes #5318.
      d0c3defe
  5. 17 May, 2018 1 commit
  6. 09 May, 2018 3 commits
  7. 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
  8. 28 Apr, 2018 1 commit
  9. 26 Apr, 2018 8 commits
  10. 19 Apr, 2018 4 commits
  11. 05 Apr, 2018 1 commit
  12. 28 Mar, 2018 1 commit
  13. 27 Mar, 2018 2 commits
  14. 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
  15. 25 Mar, 2018 3 commits
  16. 23 Mar, 2018 1 commit