Repository : ssh://darcs.haskell.org//srv/darcs/packages/Cabal

On branch  : master

http://hackage.haskell.org/trac/ghc/changeset/64e4bc88724ce2d76fa60fc31791395a079a662f

>---------------------------------------------------------------

commit 64e4bc88724ce2d76fa60fc31791395a079a662f
Author: Duncan Coutts <[email protected]>
Date:   Wed Feb 20 11:06:37 2008 +0000

    Use a dependency graph rather than a list when installing packages
    This allows us to figure out what to do when installing a single package
    fails. Instead of just carrying on as if nothing had happened and then
    failing several other packages which depended on the one that failed
    initially we can cut those dependent packages out as soon as the first one
    fails and if there is anything left that did not depend on the failed
    package then we can try and carry on.

 cabal-install/Hackage/DepGraph.hs   |  101 +++++++++++++++++++++++++++++++++++
 cabal-install/Hackage/Dependency.hs |   37 ++++++++-----
 cabal-install/Hackage/Fetch.hs      |    4 +-
 cabal-install/Hackage/Info.hs       |    6 ++-
 cabal-install/Hackage/Install.hs    |   34 +++++++-----
 cabal-install/Hackage/Utils.hs      |    4 ++
 6 files changed, 156 insertions(+), 30 deletions(-)


Diff suppressed because of size. To see it, use:

    git show 64e4bc88724ce2d76fa60fc31791395a079a662f

_______________________________________________
Cvs-libraries mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-libraries

Reply via email to