| Summary: | Please mark dev-lang/ghc-6.12.3 as stable | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lennart Kolmodin (RETIRED) <kolmodin> |
| Component: | New packages | Assignee: | Gentoo's Haskell Language team <haskell> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ppc64, ppc |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 339153, 339155, 339161, 339580, 344343 | ||
|
Description
Lennart Kolmodin (RETIRED)
2010-09-25 10:01:34 UTC
Slightly amending requested keywords: ppc64 does not have TH support, and sparc does have So requested STABLEREQ arches are: amd64 ppc sparc x86 Thanks! amd64 done Is there no nicer way to handle this?: devmanual: No combination of USE flags should cause a package to fail to build because users can set any combination of flags. * CPV: dev-lang/ghc-6.12.3 * REPO: gentoo * USE: bash-completion binary elibc_glibc ghcbootstrap kernel_linux test userland_GNU x86 * You requested ghc bootstrapping, this is usually only used * by Gentoo developers to make binary .tbz2 packages for * use with the ghc ebuild's USE="binary" feature. * ERROR: dev-lang/ghc-6.12.3 failed: * USE="ghcbootstrap binary" is not a valid combination. * * Call stack: * ebuild.sh, line 54: Called pkg_setup * ghc-6.12.3.ebuild, line 137: Called die * The specific snippet of code: * use binary && \ * die "USE=\"ghcbootstrap binary\" is not a valid combination." * * If you need support, post the output of 'emerge --info =dev-lang/ghc-6.12.3', * the complete build log and the output of 'emerge -pqv =dev-lang/ghc-6.12.3'. * The complete build log is located at '/var/tmp/portage/dev-lang/ghc-6.12.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/ghc-6.12.3/temp/die.env'. * S: '/var/tmp/portage/dev-lang/ghc-6.12.3/work/ghc-6.12.3' We've tried a few different things in the past, but finally settled for this solution. I don't see why it should be any trouble, though; * 'ghcbootstrap' is only used for dev-lang/ghc, no other package. * It's used to bootstrap the new ghc based on the systems currently installed ghc, which is for developers and possibly some advanced users. As the description says: "Internal: Bootstrap GHC from an existing GHC installation.". It's not for anybody. We use this scheme for all ghc versions and I haven't heard any user complaints so far. It would be bad if it would be common flags, and you would accidentally hit this "feature". Like, for example, you have USE="qt4 gnome" and your ebuild only could support one of them and die otherwise. But, this is not the case here. I hope this explains at least part of our reasoning. Thank you for your interest in the matter, cheers. Ok, seems reasonable to me. I've been building some rdeps and I saw some build failures that I'll check out (see if they are already reported). One thing that I noticed is that x86 stable hmake depends on ghc-6.8, do we want to have an newer version for this ghc? There is no newer version in tree yet. Bug 330095 comment #5: We'll bump stable darcs with ghc, so closing the bug as WONTFIX. As this ghc is planned to go stable, we'll need a newer dev-vcs/darcs. We'll be breaking darcs if we don't do this (and description mentions it to use as a test case). Is there any blockers for x86? I successfully upgraded my both PC. Seems like all works fine. (In reply to comment #7) > Is there any blockers for x86? I successfully upgraded my both PC. Seems like > all works fine. Yes: Compile time during testing :) I'm on it, bear with us. x86 done. Thanks a lot Myckel! Awesome, thanks! I know it's a lot to test :) sparc done.
Marked stable:
dev-lang/ghc-6.12.3
dev-haskell/cabal-1.8.0.6-r1
app-admin/haskell-updater-1.1.0.0
dev-haskell/haddock-2.6.1
Adding
alpha
ia64
ppc64
to CC as we have binaries for them for quite a while too.
alpha/ia64 done ppc/ppc64 stable |