virtual/ghc is set to be dev-lang/ghc-bin in profiles/base/virtuals. This should not be changed for any arch. Currently all ppc profiles (and the new ppc64 subprofile) override this and set virtual/ghc to resolve to dev-lang/ghc by default. This breaks the installation of ghc for ppc users that do not already have ghc or ghc-bin installed. dev-lang/ghc-bin is not like other '-bin' ebuilds. It's not an optional precompiled version. It is essential for bootstrapping dev-lang/ghc. ghc requires ghc to compile itself. We break this cycle by having a ghc-bin ebuild and making ghc depend on virtual/ghc. Both ghc and ghc-bin provide virtual/ghc. However for this to work, it is esential that virtual/ghc default to ghc-bin. Otherwise, upon trying to emerge ghc, portage would just emerge ghc rather than first emerging ghc-bin.
Fixed, thanks for spotting it
So do we not care about: ppc/2005.1/ppc64/32bit-userland ppc/2005.0 ppc/2004.3 and all older profiles? I just wanted to double check. If you're happy that these other profiles are unused/obsolete then we're fine.
Apparently ppc/2005.0 is not deprecated yet so it should probably be fixed.
Any word on this?
We're waiting for the cleaning lady.
This is fixed in all profiles as far as I can tell, please reopen the bug if this isn't the case.
