This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 17 May, 2013 1 commit
    • Mikhail Glushenkov's avatar
      Make newly-added add-source deps override previously installed versions. · e8742a5c
      Mikhail Glushenkov authored
      Fixes #1197.
      
      This patch is a bit large because it includes several related changes:
      
      1) Remove 'installUseSandbox' from 'InstallFlags' and pass 'useSandbox' as an
      additional argument instead.
      
      2) Instead of calling 'reinstallAddSourceDeps' from 'installAction', always pass
      'SandboxPackageInfo' to 'install'.
      
      3) Set the timestamps of newly-added add-source deps to 0 in the timestamp file.
      
      4) Move the timestamp file update to 'postInstallActions' from
      'withModifiedDeps'. This way, the timestamps are updated even when the user runs
      'install --only-dependencies' or 'install some-add-source-dep-package-id'.
      e8742a5c
  2. 13 May, 2013 2 commits
  3. 28 Apr, 2013 1 commit
  4. 24 Apr, 2013 2 commits
  5. 23 Apr, 2013 1 commit
  6. 19 Apr, 2013 1 commit
  7. 12 Apr, 2013 1 commit
  8. 07 Mar, 2013 1 commit
  9. 03 Mar, 2013 2 commits
  10. 08 Feb, 2013 1 commit
  11. 11 Jan, 2013 2 commits
    • refold's avatar
      7888be19
    • refold's avatar
      Replace the 'unpack' command with a more general 'get'. · f8665a4c
      refold authored
      'cabal get PACKAGE' is the new name of 'cabal unpack'.
      
      'cabal get --source-repository' reads the source-repositories from a package's
      description, determines which VCS to use, and then creates a local repository or
      branch of the package's repository.
      
      'cabal get --source-repository=[head|this|...]' additionally allows to specify
      which source-repository to use.
      
      Based on the code originally written by John Millikin <jmillikin@gmail.com>.
      f8665a4c
  12. 18 Dec, 2012 1 commit
  13. 13 Dec, 2012 2 commits
  14. 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
  15. 24 Nov, 2012 1 commit
  16. 16 Nov, 2012 1 commit
  17. 05 Nov, 2012 3 commits
  18. 14 Oct, 2012 1 commit
  19. 10 Oct, 2012 1 commit
  20. 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
  21. 24 Aug, 2012 1 commit
  22. 16 Aug, 2012 1 commit
  23. 13 Aug, 2012 3 commits
  24. 10 Aug, 2012 1 commit
  25. 09 Aug, 2012 2 commits
  26. 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
  27. 16 Apr, 2012 1 commit
  28. 06 Apr, 2012 1 commit
    • 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