This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 31 Aug, 2008 8 commits
  2. 30 Aug, 2008 1 commit
    • Duncan Coutts's avatar
      Merge PackageSet and PackageIndex · eea57172
      Duncan Coutts authored
      Have just a single module that provides both the case sensitive and
      insensitive operations. Turns out we hardly use the case insensitive
      operations, and the places where we do are not performance sensitive
      at all. So we use the PackageSet implementation which stores the
      packages case sensitively and tack on the case insensitive operations
      but with linear time implementations rather than log time. For the
      merged module/type name use PackageIndex because that is what older
      released versions exported, so less needless client breakage.
      eea57172
  3. 27 Aug, 2008 1 commit
  4. 28 Aug, 2008 3 commits
  5. 27 Aug, 2008 1 commit
    • Ian Lynagh's avatar
      Add support for manually en/disabled flags · 42a78991
      Ian Lynagh authored
      The immediate use for these is so that, in haddock, we can require
      ghc-paths normally, but in the GHC build we can manually turn off a flag
      so that this dependency isn't needed. We can't use a normal flag, or
      in the normal build Cabal would infer that the flag needs to be turned
      off if ghc-paths isn't available.
      42a78991
  6. 26 Aug, 2008 3 commits
  7. 24 Aug, 2008 2 commits
  8. 25 Aug, 2008 2 commits
  9. 24 Aug, 2008 1 commit
  10. 22 Aug, 2008 2 commits
  11. 02 Aug, 2008 1 commit
  12. 21 Aug, 2008 3 commits
    • Duncan Coutts's avatar
      Fix for #333, "Setup sdist --snapshot fails" · 0113cfea
      Duncan Coutts authored
      Credit to Spencer Janssen. This is just a slight alternative
      to the fix he proposed. It simplifies prepareSnapshotTree.
      0113cfea
    • Simon Marlow's avatar
      Don't pass cc-options to Haskell compilations · 52264c5d
      Simon Marlow authored
      This has no effect with GHC 6.9, and with earlier GHC's it was a
      misuse of cc-options.
      52264c5d
    • 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
  13. 18 Aug, 2008 1 commit
  14. 13 Aug, 2008 1 commit
  15. 14 Aug, 2008 1 commit
  16. 13 Aug, 2008 4 commits
  17. 12 Aug, 2008 5 commits