On 11/24/08, Tonko <[EMAIL PROTECTED]> wrote: > I didn't know the emaint command, but I tried it and it didn't work. > It still wants to remove gcc-3 even though I need that for qemu-softmmu.
It seems that the ebuilds for qemu-softmmu have suffered their share of bit-rot over the years: http://bugs.gentoo.org/show_bug.cgi?id=235760 Since the compile-time gcc-3 dependency is not mentioned in DEPENDS, portage and it's helpers cannot figure out that the older gcc should be kept. And since gcc version on the other hand *is* checked in the pkg_setup, it will bite in the rear ends of --binpkg users. Basically, it's a lose-lose situation with the current ebuild. It would need some reworking -- just as the bug report points out. I'm sorry, I have no explicit good solution (short of fixing that ebuild). Maybe you could copy the current ebuild of qemu-softmmu to your own overlay on that system and add the gcc-3 dependency there to the DEPENDS in the ebuild? Name it as -rX, X being the same or higher as the current in portage, emerge it once, and portage and its automagic tools should remain happy for a while. You can undo the kludge when the real portage tree catches up with the dependencies. -- Arttu V.
