This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 09 May, 2018 2 commits
  2. 08 May, 2018 2 commits
    • 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
    • quasicomputational's avatar
      218c7bfc
  3. 07 May, 2018 1 commit
  4. 03 May, 2018 1 commit
  5. 29 Apr, 2018 2 commits
  6. 28 Apr, 2018 1 commit
  7. 27 Apr, 2018 3 commits
    • Mikhail Glushenkov's avatar
      Update AUTHORS. [ci skip] · ca5ae794
      Mikhail Glushenkov authored
      ca5ae794
    • quasicomputational's avatar
    • quasicomputational's avatar
      travis: Move the 8.4.1 builders to 8.4.2. · c18df61c
      quasicomputational authored
      This ought to fix the build matrix. I believe the issue is GHC trac
      5129, where evaluate is being miscompiled: in cabal-testsuite's
      Test.Cabal.Server, in the function readUntilEnd, the 'read' function
      is protected by an 'if' to ensure that it doesn't result in the
      dreaded 'no parse'. However, some sophisticated putStrLn
      debugging has revealed that it is being called in *both* branches, not
      just the safe one; this is the worst sort of heisenbug because it
      vanished when I put a putStrLn before the evaluate!
      
      Since the evaluate function is fixed in 8.4.2 and bumping to 8.4.2
      has a patch for trac 5129, this is as fixed as it can get.
      c18df61c
  8. 26 Apr, 2018 10 commits
  9. 23 Apr, 2018 2 commits
  10. 19 Apr, 2018 7 commits
  11. 18 Apr, 2018 3 commits
  12. 17 Apr, 2018 3 commits
  13. 16 Apr, 2018 2 commits
  14. 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