This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 08 Apr, 2014 1 commit
  2. 01 Mar, 2014 1 commit
    • Daniel Trstenjak's avatar
      More diff friendly pretty printing of cabal files · 73dd1c26
      Daniel Trstenjak authored
      Now the 'fieldGet' function of 'FieldDescr' does the
      whole pretty printing of the field. Previously only the
      values have been pretty printed by 'fieldGet' and the
      name of the field with the colon have been printed
      in the 'PrettyPrint' module.
      
      But this separation made it more difficult to handle the
      pretty printing of fields differently, because some fields
      should be just printed in one lines and others - having several
      values - should be printed nested with each value on a new line.
      
      This difference in the printing of the fields is now handled by
      the 'FieldDescr' constructor functions in 'ParseUtils'.
      
      Now the 'listField' and 'commaListField' functions create 'FieldDescr'
      that nest their values and all other functions create one line
      for the whole field.
      73dd1c26
  3. 22 Feb, 2014 1 commit
  4. 02 Feb, 2014 1 commit
  5. 08 Jan, 2014 1 commit
    • Duncan Coutts's avatar
      New license-files field. · a7b58b1f
      Duncan Coutts authored
      Based closely on the patches by Mathieu Boespflug <mboes@cs.mcgill.ca>
      
      This field is intended to be used instead of (or in addition to) the
      normal 'license-file' field by packages that have multiple files for
      their license material. This is useful when eg the license is
      supplemented by additional permissions and/or conditions. Notably,
      the LGPL is structured in this way: it amends the GPL with additional
      permissions, therefore one should distribute both the GPL in COPYING
      and the LGPL in COPYING.LESSER.
      
      So we keep both the license-file and license-files fields (rather than
      deprecating one) and packages can use either or a mixture.
      a7b58b1f
  6. 17 Dec, 2013 2 commits
  7. 28 Oct, 2013 1 commit
  8. 21 Aug, 2013 1 commit
  9. 11 Jul, 2013 1 commit
  10. 10 Jul, 2013 1 commit
  11. 02 May, 2013 1 commit
  12. 14 Jan, 2013 1 commit
    • John Wiegley's avatar
      Add extra-html-files, for installing extra html files · 49a2be96
      John Wiegley authored
      For example, you might have an images/ directory in your project, with
      images that you refer to from Haddock with:
      
          <<images/foo.png>>
      
      Then in your Cabal file you would include:
      
          extra-html-files: images/*.png
      
      And these would both be packaged by sdist, and "cabal haddock" will
      install them in:
      
          ~/.cabal/share/doc/PROJECT/html/images/*.png
      
      Fixes #1167
      49a2be96
  13. 18 Nov, 2012 2 commits
  14. 03 Nov, 2012 1 commit
  15. 11 Aug, 2012 1 commit
  16. 23 Oct, 2011 1 commit
  17. 11 Oct, 2011 1 commit
  18. 25 Aug, 2011 1 commit
  19. 19 Jun, 2011 1 commit
  20. 01 Apr, 2011 1 commit
    • ttuegel's avatar
      Fix for test suite stanzas with conditionals. · 3922bde0
      ttuegel authored
      Ticket #811. This fixes a problem where Cabal would fail to detect the "type"
      field of a test suite when the test suite contained a conditional. Conditionals
      can now be used, with the restriction that the "type" field and the appropriate
      "main-is" or "test-module" field must be specified together in any conditional
      branch where they occur.
      3922bde0
  21. 26 Oct, 2010 1 commit
  22. 18 Oct, 2010 3 commits
  23. 11 Oct, 2010 1 commit
  24. 29 Sep, 2010 2 commits
  25. 16 Oct, 2010 1 commit
  26. 13 Oct, 2010 1 commit
    • Duncan Coutts's avatar
      Change the syntax and behaviour of the cabal-version field · 520b3481
      Duncan Coutts authored
      For historical reasons the cabal-version is specified with a version range,
      to indicate the range of versions of tools that the package will work with.
      We now think it makes more sense to specify the version of the Cabal spec
      that the package follows. Old Cabal versions will not be able to parse simple
      versions in this field. So we initially make the parser allow plain versions
      but then we add a check to warn about using it prior to Cabal-1.12 at which
      point it will be allowed.
      Added a check about using version ranges that are not of the form '>= x.y'.
      Also change behaviour to ignore upper bounds in the given version range.
      520b3481
  27. 10 Oct, 2010 2 commits
  28. 03 Aug, 2010 1 commit
  29. 09 Oct, 2010 1 commit
  30. 16 Jun, 2010 2 commits
  31. 09 Jun, 2010 1 commit
    • ttuegel's avatar
      Parsing TestSuite through intermediate data structure · c6aeef43
      ttuegel authored
      Ticket #215 (Overhaul support for packages' tests).  By parsing the test suite
      stanza through an intermediate data structure, we can isolate errors due to
      missing required fields in the parsing stage and avoid having error handlers
      througout the code.
      c6aeef43
  32. 08 Jun, 2010 1 commit
  33. 07 Jun, 2010 1 commit