dons:
> Hey guys,
>
> Here's a summary of what builds out of the box, and what doesn't, from
> hackage, with today's amd64 GHC RC. The initial system was just GHC
> 6.10, with cabal-install from darcs (the upcoming cabal-install
> release).
My next attempt was again, 6.10, cabal-install from darcs, but with a
'soft constraint' for base<4 (a new feature in cabal-install). This
allowed
$ ghc-pkg list --user --simple-output | wc -w
318
318 packages to build out of the box, compared to 238 without. In
particular, this enabled X11 and QuickCheck to build, and then most
things depending on it continued to build.
------------------------------------------------------------------------
Main problem now, particular, network-2.2.0.0 is failing under cabal-install,
outside of the network tree, cabal-install assigns:
Dependency base -any && ==4.0.0.0: using base-4.0.0.0
Dependency parsec -any && ==2.1.0.1: using parsec-2.1.0.1
which will fail. But notably, inside the network source tree,
cabal-install does pick base-3.
However, network-2.2.0.0 is also installed by the GHC release candidate,
with dependencies,
depends: base-4.0.0.0 parsec-2.1.0.1 syb-0.1.0.0
Ian, did you not bump the version number for the network that GHC RC provides?
If the dependencies have changed, then cabal-install will try to reinstall it,
leading to this chaos.
Time to bump those extralib versions and release them!
-- Don
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
