This project is mirrored from Pull mirroring updated .
  1. 03 Oct, 2014 1 commit
    • Edward Z. Yang's avatar
      Switch InstallPlan over to using IPID-indexed PackageIndex. · ff6c718b
      Edward Z. Yang authored
      While this doesn't let us get rid of Distribution.Client.PackageIndex,
      it does make InstallPlan more flexible, so we can have the same
      package name-package version in the install plan multiple times.
      We do this by synthesizing fake installed package IDs to act
      as placeholders prior to compilation.
      There is some shindig with 'FakeMap' in PackageIndex, check out
      the Note in that file for more details.
      This reverts commit a5a0f8e1959003ee702c04a23375a60d48f03f90, with
      a bugfix for linearizeInstallPlan.
      Fixes #2123
  2. 28 Sep, 2014 5 commits
  3. 27 Sep, 2014 1 commit
    • Herbert Valerio Riedel's avatar
      Re-allow `configure-option` in config file (re #2122) · 07030ef3
      Herbert Valerio Riedel authored
      A couple of settings were filtered out since
      74cb2909 including
      `configure-option`. However, it turns out you may want to
      persist some options to `configure`, such as e.g.
      when working in a Cygwin host environment, but using a Mingw
      toolchain (such as the one bundled with the Windows GHC bindist).
      Approved by @dcoutts
  4. 26 Sep, 2014 2 commits
  5. 25 Sep, 2014 2 commits
  6. 24 Sep, 2014 1 commit
  7. 23 Sep, 2014 1 commit
  8. 22 Sep, 2014 1 commit
    • Edward Z. Yang's avatar
      Fix three bugs with fake-map implementation for PackageIndex. · f59bab10
      Edward Z. Yang authored
      1. When we union PackageIndexes together, prefer the later one.
         This idiom is used when we update the processing-state of
         packages in an InstallPlan.
      2. dependencyInconsistencies' was missing a number of indirections
         through the fakeMap, so in some cases we incorrectly concluded
         packages were not equal when they were.
      3. We need to initialize the fakeMap with any pre-installed packages,
         otherwise the invariant check for configured-packages will fail.
      Signed-off-by: default avatarEdward Z. Yang <>
  9. 19 Sep, 2014 1 commit
  10. 18 Sep, 2014 2 commits
  11. 17 Sep, 2014 2 commits
  12. 15 Sep, 2014 1 commit
  13. 13 Sep, 2014 1 commit
    • PeterTrsko's avatar
      Bash completion for "cabal sandbox" subcommands · d00697fa
      PeterTrsko authored
      Command "cabal sandbox --list-options" doesn't list subcommands of
      "cabal sandbox", but "cabal help sandbox" does. It turns out that it is
      easy to parse its output using sed and as such can be added to list of
      words for completion.
  14. 10 Sep, 2014 2 commits
  15. 06 Sep, 2014 2 commits
    • barmston's avatar
      cabal-install tests use locally built cabal · 3f99cc0c
      barmston authored
      When running the cabal-install tests, we want to run against the locally built
      cabal executable, not any other cabal executable which may be installed.
      If we are 1) following the advice of building cabal with `cabal build` (as
      opposed to installing it into a sandbox with `cabal install`) and 2) not using
      a non-default build directory, the locally built cabal will be located at
      By adding the directory `dist/build/cabal` to the program search path we will
      pick up any cabal executable there in preference to any other on the $PATH.
      For most users, I expect that this will remove any surprises with an
      unexpected cabal executable being selected for running the tests. It will be
      sufficient to allow the tests to run on Travis.
      For users who have been installing cabal into a sandbox, this change could
      result in an older cabal executable being selected. It's not clear to me how
      to solve this issue or whether anyone will experience this.
    • barmston's avatar
      Exec tests no longer fail if there isn't a sandbox · 4b364b93
      barmston authored
      The tests which delete the sandbox, now check for its existence before
      deleting it. This prevents erroneous test failures when the tests are first
      run or any time that the sandbox has been deleted.
  16. 27 Aug, 2014 3 commits
  17. 26 Aug, 2014 2 commits
  18. 25 Aug, 2014 1 commit
    • Mikhail Glushenkov's avatar
      Bump version. · 7a24dd6a
      Mikhail Glushenkov authored
      So that the 'install_from_tarball' build bot step doesn't try to use the old
      1.21 snapshot that comes with GHC HEAD.
  19. 24 Aug, 2014 1 commit
  20. 22 Aug, 2014 2 commits
  21. 19 Aug, 2014 2 commits
  22. 18 Aug, 2014 2 commits
  23. 13 Aug, 2014 2 commits