This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 06 Mar, 2015 1 commit
  2. 04 Mar, 2015 1 commit
  3. 01 Mar, 2015 1 commit
  4. 23 Feb, 2015 1 commit
  5. 17 Jan, 2015 1 commit
  6. 10 Dec, 2014 2 commits
    • Luite Stegeman's avatar
      use CompilerInfo rather than CompilerId for resolving flags and · 7d91b773
      Luite Stegeman authored
      path templates.
      
      CompilerInfo contains more information about the compiler than
      CompilerId, which just stores the flavour and version. In particular,
      CompilerInfo knows an AbiTag, which can be used to tell binary
      incompatible results from the same compiler apart, and detailed
      information about supported languages and extensions.
      
      Some fields in CompilerInfo may be left unknown (Nothing). This can
      be used in the future to allow partially resolving configurations
      based on supported languages or extensions.
      7d91b773
    • Luite Stegeman's avatar
      Add the js-sources and various ghcjs-options fields to PackageDescription · 81330d03
      Luite Stegeman authored
      This patch adds the js-sources field, for JavaScript source code
      that should be included in compiled programs, similar to c-sources
      for other targets.
      
      It also adds ghcjs-options, ghcjs-shared-options and ghcjs-prof-options
      and makes the underlying code for options easier to extend.
      81330d03
  7. 26 Nov, 2014 1 commit
    • Edward Z. Yang's avatar
      Preliminary support for compiling signature files, using --instantiate-with. · 0ef39071
      Edward Z. Yang authored
      There's no chrome here, but some of the guts for Cabal supporting compiling
      signatures.  The key UI is a new --instantiate-with flag for ./Setup (no support
      cabal-install side!) which properly modifies the package key, calculates extra
      hole dependencies for a package, and ensures an appropriately
      translated -sig-of is passed to GHC.  The UI here is supremely user-unfriendly:
      the intent is that users will use cabal-install to calculate these parameters
      for them.
      
      ToDo: Cabal's inconsistency check in ./Setup needs to be adjusted to be
      less zealous.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      0ef39071
  8. 03 Nov, 2014 2 commits
  9. 01 Nov, 2014 1 commit
  10. 19 Oct, 2014 1 commit
  11. 18 Oct, 2014 1 commit
  12. 07 Oct, 2014 3 commits
  13. 18 Sep, 2014 1 commit
  14. 27 Aug, 2014 1 commit
    • Duncan Coutts's avatar
      Change rep of module re-exports, and do resolution ourselves · a3d3273a
      Duncan Coutts authored
      The initial support for module re-exports relied on ghc-pkg to resolve
      user-specified re-exports to references to specific installed packages.
      This resolution is something that can fail so it's better for Cabal to
      do it during the package configure phase.
      
      In addition, it is inconvenient in ghc-pkg to be doing this resolution,
      and it just seems fishy as a design. Also, the same ModuleExport type
      was being used both for user-specified source re-exports and also for
      the specific re-exports in the package db.
      
      This patch splits the type into two: one for source level, and one for
      resolved ones for use in the package db. The configure phase resolves
      one to the other.
      
      One minor change: it is now possible to re-export a module defined in
      the same package that is not itself exported (ie it's in other-modules,
      rather than exposed-modules). Previously for modules definied in the
      same package they had to be themselves exported. Of course for
      re-exports from other packages they have to be exposed.
      a3d3273a
  15. 17 Jul, 2014 1 commit
  16. 16 Jul, 2014 1 commit
    • Edward Z. Yang's avatar
      Implement "reexported-modules" field, towards fixing GHC bug #8407. · 62450f9a
      Edward Z. Yang authored
      Re-exported modules allow packages to reexport modules from their
      dependencies without having to create stub files.  Reexports of the same
      original module don't count as ambiguous imports when module finding
      occurs.  The syntax is:
      
          "orig-pkg" OrigName as NewName
      
      You can omit 'as NewName', in which case it is reexported as the same
      name.  Self referential aliases work too; however, they're only visible
      to packages which depend on this package.
      
      Left to future work: just provide a module name 'OrigName', where ghc-pkg
      figures out what the source package is.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      62450f9a
  17. 12 Jun, 2014 1 commit
  18. 12 May, 2014 1 commit
  19. 24 Apr, 2014 3 commits
  20. 17 Apr, 2014 1 commit
    • Daniel Trstenjak's avatar
      More diff friendly pretty printing of cabal files · 1ecd69c7
      Daniel Trstenjak authored
      Added the new field constructor functions 'listFieldWithSep'
      and 'commaListFieldWithSep' to be able to define pretty printing
      for fields, where each value of the field is positioned on a new line.
      
      Which fields are nested is currently hard coded in the 'ppField' function.
      
      (cherry picked from commit e8d5ea25)
      1ecd69c7
  21. 16 Apr, 2014 1 commit
    • Daniel Trstenjak's avatar
      More diff friendly pretty printing of cabal files · e8d5ea25
      Daniel Trstenjak authored
      Added the new field constructor functions 'listFieldWithSep'
      and 'commaListFieldWithSep' to be able to define pretty printing
      for fields, where each value of the field is positioned on a new line.
      
      Which fields are nested is currently hard coded in the 'ppField' function.
      e8d5ea25
  22. 14 Apr, 2014 2 commits
  23. 12 Apr, 2014 1 commit
    • Daniel Trstenjak's avatar
      Fixed pretty printing of fields · fdf8afce
      Daniel Trstenjak authored
      The list constructors 'nestedListField' and 'nestedCommaListField'
      have been added and are now used for fields that should be pretty
      printed with nesting.
      fdf8afce
  24. 10 Apr, 2014 3 commits
  25. 08 Apr, 2014 2 commits
  26. 21 Mar, 2014 1 commit
  27. 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
  28. 22 Feb, 2014 1 commit
  29. 02 Feb, 2014 1 commit
  30. 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