This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 30 Jul, 2008 2 commits
    • Duncan Coutts's avatar
      Add support to SetupWrapper for logging setup output to a handle · 0d2c5f6c
      Duncan Coutts authored
      or for using a diiferent initial working directory. We already
      need to use a different working dir and this would allow us to
      spawn multiple setup processes for parallel builds each with
      their own working dir. Also, we want to be able to capture the
      output of builds. At the moment our internal logging framework
      is not capable of redirecting, but if we launch a process we
      redirect its output to a file. This should be useful for build
      reporting where we want logs for each individual package.
      0d2c5f6c
    • Duncan Coutts's avatar
      Move modules under Distribution.Client · dff86f85
      Duncan Coutts authored
      And tidy some imports slightly
      dff86f85
  2. 25 Jul, 2008 1 commit
  3. 23 Jun, 2008 1 commit
  4. 19 Jun, 2008 1 commit
  5. 18 Jun, 2008 1 commit
  6. 17 Jun, 2008 2 commits
  7. 16 Jun, 2008 5 commits
  8. 13 Jun, 2008 1 commit
  9. 12 Jun, 2008 5 commits
  10. 10 Jun, 2008 6 commits
  11. 09 Jun, 2008 1 commit
  12. 08 Jun, 2008 3 commits
  13. 07 Jun, 2008 2 commits
    • Duncan Coutts's avatar
      Use a smarter preference when picking a Cabal lib to build Setup.hs · 9d650d2c
      Duncan Coutts authored
      Instead of just using the latest version we use the best version
      according to the following preferences in priority order:
      - the same version as cabal-install was itself built with
      - the same major version number as cabal-install was built with
      - a stable version of Cabal (even second digit of major number)
      - the latest version
      9d650d2c
    • Duncan Coutts's avatar
      Only inspect the needed parts of the installed and available indexes · 8d9cef62
      Duncan Coutts authored
      The available package index is loaded lazily so if we can avoid
      forcing all the packages then we can save a huge amount of slow text
      parsing. So select out the maximal subset of the index that we could
      ever need based on the names of the packages we want to install. For
      the common case of installing just one or two packages this cuts
      down the number of packages we look at by a couple orders of
      magnitude. This does not help with the installed index which is read
      strictly, though most people do not (yet) have hundreds of installed
      packages, so that's less of an immediate problem.
      8d9cef62
  14. 06 Jun, 2008 9 commits