This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 08 May, 2016 7 commits
  2. 07 May, 2016 5 commits
    • Mikhail Glushenkov's avatar
      Merge pull request #3376 from dcoutts/master · 7e8ea4ca
      Mikhail Glushenkov authored
      Adjustments for what deps we pick for legacy Setup scripts in new-build
      7e8ea4ca
    • Duncan Coutts's avatar
      Adjust the Cabal dep constraint for legacy Setup.hs scripts · 29b7c904
      Duncan Coutts authored
      Add a lower bound of >= 1.18. Also improve the related comments.
      
      Using >= 1.18 since we currently have problems working with 1.16 as that
      version lacks support for named build targets. We ought to fix working
      with older versions though.
      29b7c904
    • Duncan Coutts's avatar
      Adjust the default set of Setup.hs deps for legacy scripts · 58021348
      Duncan Coutts authored
      Add transformers and old-time, and for ghc-compatible compilers also add
      ghc-prim and template-haskell.
      
      Have to double check if the old-time dep needs to be conditional, e.g.
      on ghc version.
      58021348
    • Duncan Coutts's avatar
    • Duncan Coutts's avatar
      Report process output decoding errors in context · cc35a48a
      Duncan Coutts authored
      It turns out that in rawSystemStdInOut any IO errors, including text
      decoding, occurring while collecting the output (stderr or stdout) do
      not get reported immediately, but only later if/when the output is
      consumed. This is because the exceptions happened in the threads forked
      to force the output, but if the main thread looks at the output later
      then the exception is reported again.
      
      This leads to very confusing results. In particular we had a case where
      the configure process did not fail until writing out the LocalBuildInfo
      because that was the first point that forced the output. So the distance
      from when the exception really occurred and the fact that the exception
      message does not include the name of the program run means that this is
      then a pain to track down.
      
      This patch makes sure that any exceptions arising from forcing the
      program output occur immediately and with an error message that includes
      the name of the program in question.
      cc35a48a
  3. 06 May, 2016 13 commits
  4. 05 May, 2016 2 commits
  5. 04 May, 2016 12 commits
  6. 03 May, 2016 1 commit