This project is mirrored from Pull mirroring updated .
  1. 08 Jul, 2011 1 commit
    • ttuegel's avatar
      Don't prefix test output with ">>>". · 51a4e402
      ttuegel authored
      Ticket #848. Removing the prefix brings "cabal test" in line with other cabal
      commands, which do not prefix their output, either. Prior to this patch, the
      summary notices which appear before and after each test suite were written to
      the temporary log file along with the stdio from the test executable; this would
      lead to duplicate notices when the contents of the temporary log file are read
      onto the console. After this patch, the summary notices are never written to the
      temporary log file, only to the console and the final log file (which is never
      read by Cabal), removing the confusing duplicate notices.
  2. 03 Mar, 2011 1 commit
  3. 08 Jul, 2011 4 commits
    • Duncan Coutts's avatar
      Bump cabal-install version · a448e16c
      Duncan Coutts authored
    • Duncan Coutts's avatar
      Bump Cabal lib version · d128ad3f
      Duncan Coutts authored
    • Duncan Coutts's avatar
      Couple of trivial code changes · e1d9192f
      Duncan Coutts authored
    • Duncan Coutts's avatar
      Fix withComponentsLBI and move Components to LocalBuildInfo module · 1c20a632
      Duncan Coutts authored
      An annoyance of the current Simple build system is that each phase
      (build, install, etc) can be passed additional HookedBuildInfo which
      gets merged into the PackageDescription. This means that we cannot
      process the PackageDescription up front at configure time and just
      store and reuse it later, we have to work from it each time afresh.
      The recent addition of Components (libs, exes, test suites) and a
      topoligical sort of the components in the LocalBuildInfo fell foul
      of this annoyance. The LocalBuildInfo stored the entire component
      which meant they were not updated with the HookedBuildInfo. This
      broke packages with custom Setup.hs scripts that took advantage of
      the HookedBuildInfo feature, including those with configure scripts.
      The solution is to store not the list of whole components but the
      list of component names. Then withComponentsLBI retrieves the actual
      components from the PackageDescription which thus includes the
      Also moved the Components into an internal module because (for the
      moment at least) it is part of the Simple build system, not part of
      the package description.
  4. 06 Jul, 2011 1 commit
  5. 24 Jun, 2011 1 commit
  6. 19 May, 2011 1 commit
  7. 18 Jun, 2011 1 commit
  8. 19 Jun, 2011 2 commits
  9. 21 May, 2011 1 commit
    • Duncan Coutts's avatar
      cabal init: various UI tweaks and changes to the generated .cabal files · d448be2c
      Duncan Coutts authored
      - Add a default "(none)" option for license and category. There are now no
        questions with no default except for the lib/exe question. For throwaway
        packages user can just keep hitting enter and get something sensible.
      - Prune the list of suggested licenses (remove unversioned GPL, LGPL)
      - Don't include extra-source-files or build-tools when they would be empty
      - Improve the wording of the generated documentation for lib/exe fields
  10. 17 May, 2011 3 commits
  11. 16 May, 2011 1 commit
  12. 15 May, 2011 1 commit
  13. 30 Apr, 2011 1 commit
  14. 03 May, 2011 1 commit
  15. 18 Apr, 2011 3 commits
  16. 14 Apr, 2011 2 commits
  17. 29 Mar, 2011 1 commit
  18. 27 Mar, 2011 8 commits
  19. 26 Mar, 2011 1 commit
    • Duncan Coutts's avatar
      Generalise the constraint set ADT in a couple ways · 0094c582
      Duncan Coutts authored
      We now track target packages and only require constraints on those
      targets to be satisfiable. This allows us to overconstrain packages
      that we do not care about, which is useful for excluding broken
      We also now have a more general way of specifying constraints.
      Previously constraints were specified as the conjunction of a version
      range predicate and an optional installed constraint. This form made
      it impossible to express constraints such as "exclude this source
      package". Constraints for a package name are now specified simply by
      a function predicate on the package version and installed/source state.
  20. 27 Mar, 2011 2 commits
  21. 04 Mar, 2011 1 commit
  22. 08 Mar, 2011 1 commit
  23. 15 Mar, 2011 1 commit