This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 14 May, 2008 3 commits
  2. 13 Apr, 2008 1 commit
  3. 14 May, 2008 7 commits
  4. 13 May, 2008 1 commit
  5. 11 May, 2008 3 commits
  6. 10 May, 2008 1 commit
    • Ian Lynagh's avatar
      Fix a bug in the unlitter · 9450a27f
      Ian Lynagh authored
      If we see a birdtrack while we are in latex mode, then we stay in latex
      mode - don't change into bird mode!
      9450a27f
  7. 09 May, 2008 1 commit
  8. 06 May, 2008 5 commits
  9. 05 May, 2008 1 commit
    • Duncan Coutts's avatar
      Cope better with ghc bug #2201, display a better error message · 87b444ce
      Duncan Coutts authored
      Otherwise it can (and does) really confuse people.
      The problem is that the command $ ghc-pkg-6.9 describe '*' --user
      returns a non-zero exit code if the user package db is empty.
      ghc-pkg intends this exit code to tell us if the query returned
      any results (one can use more complex queries as tests) but Cabal
      interprets it as failure. Indeed we cannot distinguish it from
      any other kind of failure from ghc-pkg.
      87b444ce
  10. 04 May, 2008 3 commits
  11. 01 May, 2008 7 commits
  12. 30 Apr, 2008 1 commit
  13. 29 Apr, 2008 2 commits
    • Duncan Coutts's avatar
      Change handling of bool command line args to allow an unset state · fb993c2a
      Duncan Coutts authored
      For bool valued flags we were always producing the command line
      string corresponding to a false flag value, even if the flag was
      not set. For example we'd always get "--disable-shared".
      It is important for cabal-install to be able to take an empty set
      of flags, override a few flags and turn the flags back into
      command line strings without getting a lot of extra defaults.
      Partly this is because we have to work with older versions of the
      Cabal library command line which does not recognise the new options.
      fb993c2a
    • Duncan Coutts's avatar
      Remove the feature for highlighting the default cases in --help output · d49d15a7
      Duncan Coutts authored
      Turns out it doesn't help us much because in many cases the initial/default
      flags are actually empty so we cannot identify the default values.
      d49d15a7
  14. 28 Apr, 2008 2 commits
  15. 26 Apr, 2008 1 commit
    • nominolo@gmail.com's avatar
      Fix fix for #224. · 7e69b6f4
      nominolo@gmail.com authored
      Changing from list of Dependencies to Maps resulted in the wrong Monoid 
      instance being used.  I'd still like to be able to run a test suite on 
      this but that'd require a lot more work to do properly...
      7e69b6f4
  16. 23 Apr, 2008 1 commit
    • Duncan Coutts's avatar
      When multiple specifying list fields in the same section combine them · 48c8903b
      Duncan Coutts authored
      eg if you had:
      extensions: Foo
      extensions: Bar, Baz
      then previously we only ended up with [Bar, Baz]. Now we get them all.
      Only applies to list fields, for single fields the second value is taken
      and the first is silently discarded. This isn't good of course but the
      fix is harder since we're not in a context where we can report errors.
      Really we should just declare up front what kind of field it is and
      inherit the right behaviour automagically, either duplicates disallowed
      or allowed and combined with mappend.
      48c8903b