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