This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 16 Apr, 2018 1 commit
  2. 12 Apr, 2018 1 commit
    • Edward Z. Yang's avatar
      Haddock: Generate haddock for components · f3cacffe
      Edward Z. Yang 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 these "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. The new behaviour works like this:
      
      Setting documentation: true or passing
      --enable-documentation to cabal-install enables documentation
      for any component in the build plan honoring the respective
      flags for "second class" doc targets from configuration
      or CLI.
      
      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 test suite of your package
      even if you have tests: false in your haddock configuration.
      
      Merge pull request #5226 from alexbiehl/pr/haddock-components
      f3cacffe
  3. 09 Apr, 2018 1 commit
  4. 07 Apr, 2018 2 commits
  5. 31 Mar, 2018 6 commits
  6. 28 Mar, 2018 6 commits
  7. 27 Mar, 2018 10 commits
  8. 26 Mar, 2018 4 commits
    • Herbert Valerio Riedel's avatar
      Merge master into T5164 · dd014462
      Herbert Valerio Riedel authored
      dd014462
    • 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
    • Mikhail Glushenkov's avatar
      Merge pull request #5230 from haskell/lspitzner-patch-1 · 4b72242a
      Mikhail Glushenkov authored
      Fix warning message for `cabal-version` field (see #5108)
      4b72242a
    • Mikhail Glushenkov's avatar
      Merge pull request #5233 from sergv/master · db41fbde
      Mikhail Glushenkov authored
      Fix typo [ci skip]
      db41fbde
  9. 25 Mar, 2018 5 commits
  10. 24 Mar, 2018 1 commit
  11. 23 Mar, 2018 3 commits