This project is mirrored from Pull mirroring updated .
  1. 18 Sep, 2016 1 commit
    • Edward Z. Yang's avatar
      Print selected configure flags in install plan. · 52e8bfd0
      Edward Z. Yang authored
      When debugging #3827, I wished I could see what the profiling
      status of all packages in our install plan was.  This patch
      outputs this information, by printing the *configure flag*
      we would have passed to configure.
      In an ideal world, we'd print exactly the configure flags
      we actually pass in practice.  But this is not so great because
      the flag lists tend to be really long.  So we pare it down
      in the following ways:
      1. Not all flags are output: only a selected few.  In this
         patch, it's just enabling/disabling profiling flags, but
         we could add more.
      2. If we have Flag False for profiling, we will actually
         explicitly pass --disable-profiling to the configure
         script.  But it's not so good to output that to the
         user.  So 'nubFlag' lets us drop the flag, if omitting
         it would have the same effect as specifying it.
         Figuring that out is a little tricky though.
      Signed-off-by: default avatarEdward Z. Yang <>
  2. 17 Sep, 2016 1 commit
  3. 16 Sep, 2016 23 commits
  4. 15 Sep, 2016 4 commits
  5. 14 Sep, 2016 3 commits
    • Duncan Coutts's avatar
      Don't store secure index metadata in travis cache · 2e8b7df6
      Duncan Coutts authored
      Just as we don't store the package index in the cache. That said, in
      future once we're using the secure repo routinely it'd be ok to
      occasionally cache the index if we wanted, to save downloads. But since
      it does change frequently, we wouldn't want to update the cache
    • Duncan Coutts's avatar
      Be more careful about closing files before they're deleted · a534ec99
      Duncan Coutts authored
      Using withFile rather than readFile for reading temp files in the utils
      that invoke curl and wget.
      Add a dep on deepseq. This is not new since Cabal also depends on it.
    • Duncan Coutts's avatar
      Update hackage index before running integration tests · 64f5c5b8
      Duncan Coutts authored
      Now that we default to the secure repo, we need to run cabal update the
      first time before running cabal (new-)build/etc, which is essentially
      what the integration tests do. The travis and appveyor scripts already
      did a cabal update at the beginning, but this one was using the
      boostrap cabal and currently that version does not use the secure repo
      format by default.
  6. 13 Sep, 2016 8 commits