Bugzilla Bug 126134

Please mark these packages as stable on x86, amd64, sparc and ppc:

dev-lang/ghc-bin-6.4.1
dev-haskell/haddock-0.7
dev-haskell/cabal-1.1.3-r1
dev-lang/ghc-6.4.1-r2

(ghc deps on haddock and cabal)

ghc is as significant package as all the other dev-haskell packages depend on
it. A a couple other packages of interest to non-Haskell developers that depend
on ghc are in portage: darcs and pugs. Current versions of each dev-haskell
package should build with ghc-6.4.1.

ghc-6.4.1 has been in ~arch on these arches for some time. We're happy that
it's stable. In recent weeks we've been fixing bugs and problems people could
have encountered when migrating.

The haskell herd have been running migration tests in various configurations on
x86 and amd64. We've not had any problems so far. I'm still running migration
tests on sparc. Migration on ppc has not been tested.

This will be the first stable version for amd64. Previous ghc versions were
quite buggy on amd64 but I'm now confident that it's ok. I've not had any
problems on amd64 since version 6.4.1.

Known problems:
* ghc-bin-6.4.1 still suffers from having exec-stacks and it produces binaries
that have exec stacks (see bug #123698). This is fixed in ghc-6.4.1-r2 but we
didn't feel it was significant enough to be worth making new .tbz2 packages for
the ghc-bin ebuild on all our arches. This will get fixed for ghc-bin next time
we have to rebuild the .tbz2 files which will probably be for ghc-6.4.2.

* ghc-bin and ghc do not share package databases. So after changing from
ghc-bin to ghc one has to re-emerge any other haskell library ebuilds. We
provide a ghc-updater script (much like python-updater) which rebuilds haskell
library ebuilds. This works for when users upgrade their ghc version. It can
also be used to switch from ghc-bin to ghc and vica versa. Both the ghc and
ghc-bin ebuilds display a message after install to warn the users about this
and to tell them what command to run. In practice we don't think this will be a
problem (it's worked much less smoothly than it does now for some time and
we've never had bugs filed about it). We think most users who do Haskell
development go for the ghc ebuild first and then emerge libs rather than
emerging ghc-bin and then emerging some libs and then switching to ghc. The
people who only emerge ghc-bin tend not to emerge many libs we think (though it
works fine) and just use ghc-bin to build apps like pugs and darcs.

(In reply to comment #0)
> I'm still running migration tests on sparc.

This worked fine.

I've tested ghc-bin/ghc, cabal and haddock on ppc.
Everything builds smooth. I was also able to throw random packages at
ghc(-bin), no errors, the packages are just fine. Particulary darcs went all
smooth.

So no worries on the ppc front.

Stable on ppc

Thanks for testing Matti :)

Stable on sparc, thanks for your work Duncan.

x86 and amd64 stable.

Thanks everyone!