This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 31 May, 2009 1 commit
  2. 27 May, 2009 4 commits
  3. 15 May, 2009 1 commit
  4. 29 Jan, 2009 1 commit
  5. 22 Nov, 2008 1 commit
  6. 21 Nov, 2008 1 commit
  7. 21 Aug, 2008 1 commit
    • Simon Marlow's avatar
      Don't propagate cc-options to the InstalledPackageInfo · c6afec6a
      Simon Marlow authored
      cc-options is for options to be passed to C compilations in the
      current package.  If we propagate those options to the
      InstalledPackageInfo, they get passed to C compilations in any package
      that depends on this one, which could be disastrous.  I've seen
      cc-options like these:
      
         cc-options:      -optc-std=c99
         cc-options:         -D_FILE_OFFSET_BITS=64
         Cc-options:      -Wall
      
      these are all clearly intended to be local, but are in fact currently
      propagated to all dependent packages.
      c6afec6a
  8. 04 Aug, 2008 1 commit
  9. 30 Jul, 2008 1 commit
    • Duncan Coutts's avatar
      Add an "exposed" field to the .cabal file library section · aa26864e
      Duncan Coutts authored
      It's a bool flag that says if by default the library should
      be registered with the compiler as exposed/unhidden (for
      compilers which have such a concept, ie ghc). You might want
      to do this for packages which would otherwise pollute the
      module namespace or clash with other common packages.
      It should be very rarely used. The only current examples we
      know of are the ghc api package and the dph packages.
      aa26864e
  10. 28 Jun, 2008 1 commit
    • Duncan Coutts's avatar
      Update module headers · 0c993c84
      Duncan Coutts authored
      Use cabal-devel@haskell.org as the maintainer in most cases except for
      a few which were pre-existing modules copied from elsewhere or modules
      like L.H.Extension which really belong to libraries@haskell.org
      Remove the useless stability module. We have more detailed information
      on stability elsewhere (in the version number and user guide).
      Add more top level module documentation, taken from the source guide.
      0c993c84
  11. 26 Jun, 2008 1 commit
  12. 14 Jun, 2008 1 commit
  13. 16 Jun, 2008 1 commit
  14. 12 Jun, 2008 1 commit
  15. 10 Jun, 2008 1 commit
  16. 11 May, 2008 1 commit
  17. 27 Mar, 2008 1 commit
    • Duncan Coutts's avatar
      Rename various *Verbose fields to *Verbosity instead · 556b9877
      Duncan Coutts authored
      Despite appearances this is actually not completely pointless.
      For the Cabal-1.4 branch we need the *Verbose fields to have the
      same types as they did in Cabal-1.2, becuase lots of Setup.hs
      scripts use them and our change to make them all have type Flag
      makes many Setup.hs scripts fail. A solution for the 1.4 branch
      is to rename the real field and to add the old field back in.
      To keep as much similarity as possible between the HEAD and 1.4
      branches I'm applying the name change in both.
      On the plus side it's a better name anyway.
      556b9877
  18. 21 Mar, 2008 1 commit
  19. 12 Mar, 2008 1 commit
  20. 07 Mar, 2008 1 commit
  21. 04 Mar, 2008 1 commit
  22. 27 Feb, 2008 2 commits
    • Duncan Coutts's avatar
      Don't yet treat package registration files as UTF8 · 1957c176
      Duncan Coutts authored
      Though we'll probably need to do so eventually because they contain many of
      the same fields as the .cabal files which are UTF8. This will need agreement
      with ghc-pkg.
      1957c176
    • Duncan Coutts's avatar
      Revert some of the UTF8 changes, use UTF8 only for files we know are UTF8 · c99ac791
      Duncan Coutts authored
      So we use ordinary read/writeFile for ordinary text files. For console
      output we use ordinary putStr etc and we'll just hope that haskell
      implementations catch up and deal with that sensibly. Don't assume
      captured program output is UTF8, use the default encoding.
      So we use binary mode IO along with UTF8 encoding and decoding only for 
      file types that we specify to be UTF8, which are .cabal files and
      .hs/.lhs files only.
      c99ac791
  23. 24 Feb, 2008 2 commits
  24. 23 Feb, 2008 1 commit
  25. 22 Feb, 2008 2 commits
  26. 06 Feb, 2008 1 commit
  27. 05 Feb, 2008 2 commits
  28. 23 Jan, 2008 2 commits
  29. 22 Jan, 2008 2 commits
  30. 15 Dec, 2007 1 commit
    • Duncan Coutts's avatar
      Make all command line flags and flag collection types monoids · 1352ee0b
      Duncan Coutts authored
      And specify command flags in a way that allows converting from or two strings.
      So not only can we parse command lines into the various flag types, we can
      convert back. This is crucial in cabal-install so that we can call Setup.hs
      scripts with all the various args, and override certain flags in a typed way
      rather than just representing them all as strings.
      1352ee0b
  31. 08 Dec, 2007 1 commit