This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 18 Dec, 2012 1 commit
  2. 13 Dec, 2012 2 commits
  3. 26 Nov, 2012 1 commit
    • refold's avatar
      Don't pass unsupported flags to setups built with old Cabal versions. · 582d12e4
      refold authored
      We must not pass '--disable-benchmarks' to setup scripts built with Cabal <
      1.14; the same is also true for '--disable-tests' and Cabal < 1.10.
      
      Fixes #932 and #1004.
      
      Without this patch:
      
          $ cabal install -w /path/to/ghc-7.2.1/bin/ghc syb
          [...]
          unrecognized option `--disable-benchmarks'
          Failed to install syb-0.3.7
      
      With this patch:
      
          $ cabal install -w /path/to/ghc-7.2.1/bin/ghc syb
          [...]
          Registering syb-0.3.7...
          Installed syb-0.3.7
      582d12e4
  4. 24 Nov, 2012 1 commit
  5. 16 Nov, 2012 1 commit
  6. 05 Nov, 2012 3 commits
  7. 14 Oct, 2012 1 commit
  8. 10 Oct, 2012 1 commit
  9. 29 Sep, 2012 2 commits
    • Duncan Coutts's avatar
      Extend the unpack command for the .cabal file updating · 68d72430
      Duncan Coutts authored
      By default, "cabal unpack blah" will also update the .cabal file with
      the one from the index, so it's consistent with what you get via
      cabal install. Also added a --pristine flag so you can get the original
      tarball without the updated .cabal file.
      68d72430
    • Duncan Coutts's avatar
      Extend the unpack command for the .cabal file updating · b7565f94
      Duncan Coutts authored
      By default, "cabal unpack blah" will also update the .cabal file with
      the one from the index, so it's consistent with what you get via
      cabal install. Also added a --pristine flag so you can get the original
      tarball without the updated .cabal file.
      b7565f94
  10. 24 Aug, 2012 1 commit
  11. 16 Aug, 2012 1 commit
  12. 13 Aug, 2012 3 commits
  13. 10 Aug, 2012 1 commit
  14. 09 Aug, 2012 2 commits
  15. 24 Jun, 2012 2 commits
    • Duncan Coutts's avatar
      Parallelise the install command This is based on Mikhail Glushenkov's patches. · 43e5c8f1
      Duncan Coutts authored
      It adds a '-j N' (= 'number of jobs') option for the 'install' command, which
      can be used to specify the number of concurrent workers. If possible, at most
      N packages will be built concurrently.
      
      This version of the patch is less featureful than Mikhail's version but also
      rather simpler. The key difference compared to Mikhail's version is that this
      version is lacking the output serialisation and the ability to tag each output
      message with the task it came from. All output is interleaved. The next step
      will be to make parallel builds log to files rather than the console and only
      to display a summary on the console.
      
      In addition to not having to change the output functions, the code is a bit
      simpler by keep the structure of the code the same as before, rather than
      splitting it into a number of concurrent tasks with channels. Instead each
      task simply executes the same pattern of install actions and concurrency
      limits are enforced using semaphores.
      43e5c8f1
    • refold's avatar
      Add a '-j' flag for the 'install' command. · f69ff1b0
      refold authored
      f69ff1b0
  16. 16 Apr, 2012 1 commit
  17. 06 Apr, 2012 2 commits
    • Andres Löh's avatar
      make the reinstall check less noisy · 36b0c638
      Andres Löh authored
      There are two aspects to this change.
      
      The uncontroversial one is that if the install plan contains
      reinstalls, we now determine if there are reverse dependencies
      of such reinstalled packages that we can see. If so, these
      are likely to be broken. If we find such packages, we list
      them and state that we can only install the plan if
      --force-reinstalls is explicitly stated.
      
      The more controversial change is that if we cannot find such
      reverse dependencies, we now merely print a warning but
      continue, even though there are situations where executing
      the build process can still break packages. The most likely
      example of this is that we're installing to the global package
      database, and user package databases on the system have
      dependencies on the replaces packages -- but we cannot see
      these user package databases.
      36b0c638
    • Andres Löh's avatar
      d755a324
  18. 31 Mar, 2012 1 commit
    • Andres Löh's avatar
      choose default solver based on compiler version · 1a3ff039
      Andres Löh authored
      GHC-6.12 has base-3 depending on base-4. This is a situation the
      topdown solver is hacked to deal with, but the new modular solver
      currently doesn't support it. We therefore switch back to the
      topdown solver if a GHC version before 7 is detected, but switch
      to the modular solver by default in all other situations.
      1a3ff039
  19. 25 Oct, 2011 1 commit
  20. 07 Nov, 2011 1 commit
  21. 03 Nov, 2011 1 commit
  22. 28 Oct, 2011 3 commits
  23. 27 Oct, 2011 1 commit
  24. 26 Oct, 2011 1 commit
    • Jens Petersen's avatar
      add --override-reinstall-check option · a5c35062
      Jens Petersen authored
      This option flag overrides the new destructive reinstalls check,
      allowing forcing overwriting already installed library versions.
      The patch also documents this flag and other softer options
      in the output of printPlanMessages, which is renamed to checkPrintPlan.
      a5c35062
  25. 25 Oct, 2011 1 commit
  26. 09 Jul, 2011 1 commit
  27. 07 Jul, 2011 1 commit
  28. 03 Jul, 2011 1 commit
  29. 30 Jun, 2011 1 commit