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

On branch  : master

http://hackage.haskell.org/trac/ghc/changeset/40b0b1f00d745cdde2bd1e4dd16f41228f712690

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

commit 40b0b1f00d745cdde2bd1e4dd16f41228f712690
Author: Duncan Coutts <[email protected]>
Date:   Wed Jun 4 10:10:10 2008 +0000

    Failed packages can still depend on configured packages
    This is because a package can depend on several packages and if one
    of the deps fail then it fails but it still depend on the others
    that did not fail. This fixes an assertion failure in larger builds.

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

 cabal-install/Hackage/InstallPlan.hs |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/cabal-install/Hackage/InstallPlan.hs 
b/cabal-install/Hackage/InstallPlan.hs
index 11f321d..8da4e3d 100644
--- a/cabal-install/Hackage/InstallPlan.hs
+++ b/cabal-install/Hackage/InstallPlan.hs
@@ -389,6 +389,10 @@ stateDependencyRelation (Installed   _) (PreExisting _) = 
True
 stateDependencyRelation (Installed   _) (Installed   _) = True
 
 stateDependencyRelation (Failed    _ _) (PreExisting _) = True
+-- failed can depends on configured because a package can depend on
+-- several other packages and if one of the deps fail then we fail
+-- but we still depend on the other ones that did not fail:
+stateDependencyRelation (Failed    _ _) (Configured  _) = True
 stateDependencyRelation (Failed    _ _) (Installed   _) = True
 stateDependencyRelation (Failed    _ _) (Failed    _ _) = True
 



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

Reply via email to