This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 07 Mar, 2008 2 commits
  2. 06 Mar, 2008 1 commit
  3. 10 Mar, 2008 5 commits
  4. 07 Mar, 2008 3 commits
  5. 06 Mar, 2008 1 commit
  6. 05 Mar, 2008 2 commits
  7. 04 Mar, 2008 2 commits
  8. 05 Mar, 2008 2 commits
  9. 04 Mar, 2008 1 commit
  10. 03 Mar, 2008 7 commits
    • nominolo@gmail.com's avatar
      Fix speling. · 2236045c
      nominolo@gmail.com authored
      2236045c
    • nominolo@gmail.com's avatar
    • Duncan Coutts's avatar
      Actually we don't need wrapText' · 6d4b9755
      Duncan Coutts authored
      Any users of custom wrapText versions can go from the underlying wrapLine
      6d4b9755
    • Duncan Coutts's avatar
      Bump version to 1.3.7 · 1f2a7ef0
      Duncan Coutts authored
      Keep up with recent minor api changes
      1f2a7ef0
    • Duncan Coutts's avatar
      Put a header in the dist/setup-config file and check it on loading · e15289e4
      Duncan Coutts authored
      This should fix ticket #120 in future which is the problem where you do
      something like "sudo runghc Setup install" and you accidentally end up
      using a different version of the compiler or of the Cabal lib and you get
      an unhelpful error message:
      > Setup.hs: error reading ./.setup-config; run "setup configure" command?
      Well now you'll get a helpful error message:
      > setup: You need to re-run the 'configure' command. The version of Cabal
      > being used has changed (was Cabal-1.3.6, now Cabal-1.3.7).
      If the compiler version being used has changed too we get the extra helpful:
      > setup: You need to re-run the 'configure' command. The version of Cabal
      > being used has changed (was Cabal-1.3.6, now Cabal-1.3.7). Additionally
      > the compiler is different (was ghc-6.8, now ghc-6.9) which is probably
      > the cause of the problem.
      Of course this does not help for older versions of Cabal but there's not a
      lot we can do about that.
      e15289e4
    • Duncan Coutts's avatar
      Extend and use the OS data type in the package description · 3108588e
      Duncan Coutts authored
      Rather than just using a string. This makes comparing OSs easier since
      we can normalise them once when we parse rather than every time we compare.
      Also makes it easy to discover when a package mentions an unknown OS since
      it's marked as Other "whatever".
      3108588e
    • Duncan Coutts's avatar
      Wrap the output of the logging functions · 4bdbdfab
      Duncan Coutts authored
      So we'll not have to keep adjusting newline breaks.
      4bdbdfab
  11. 01 Mar, 2008 1 commit
  12. 29 Feb, 2008 3 commits
  13. 28 Feb, 2008 1 commit
  14. 27 Feb, 2008 6 commits
  15. 26 Feb, 2008 1 commit
    • Duncan Coutts's avatar
      Add liftOption for making derived command parsers · 8c5ca96a
      Duncan Coutts authored
      liftOption :: (b -> a) -> (a -> (b -> b)) -> Option a -> Option b
      For example:
      liftOption fst (\a (_,b) -> (a,b)) :: Option a -> Option (a,b)
      Needed to be able to make a CommandUI (a, b) using an existing CommandUI a.
      That's what we want to do in cabal-install where the 'install' command
      to support all the 'configure' flags and some extra of it's own, for example
      --dry-run and probably several more in future.
      8c5ca96a
  16. 25 Feb, 2008 2 commits
    • Duncan Coutts's avatar
      GHC's package db files are actually ascii, not UTF8 · c971406c
      Duncan Coutts authored
      Because they're in Haskell Read/Show format which escapes non-ascii chars
      in Strings.
      c971406c
    • Duncan Coutts's avatar
      Check for invalid UTF8 when parsing .cabal files · cf7baddf
      Duncan Coutts authored
      This assumes a permissive UTF8 decoder has inserted '\xfffd' as a replacement
      character. We should check strictly for errors when we decode instead, though
      it's nice to do that where we have some kind of error reporting infrastructure
      which is why I've added it to the parser for the moment. The current error
      message is not too bad, as it reports the line number.
      cf7baddf