[gentoo-amd64] Seamonkey vs Mozilla: pointless cage match

[felix@crowfix.com]

I have a ~amd64 system on which I am trying to emerge world.

First, what are the proper options to pass to this command?  Several
packages will not compile, and Duncan has suggested an emerge world to
clean things up.  Well, right now is a good time for me ...

Second, when I try emever -pve world, I get the following complaints:

Calculating world dependencies
..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ... done!
[blocks B     ] kde-base/kde-env (is blocking kde-base/kdelibs-3.5.5-r5)
[blocks B     ] >=kde-base/kdelibs-3.5.4-r2 (is blocking kde-base/kde-env-3-r4)
[blocks B     ] www-client/mozilla (is blocking www-client/seamonkey-1.0.6)
[blocks B     ] <dev-python/pygtk-2.9 (is blocking dev-python/pygobject-2.12.2)

1. What's the scoop on kde-env vs kdelibs?

2. Ditto for pygtk vs pygobject.

This happens aperiodically.  Some new package obsoletes another
package, but nothing documents it, nothing tells me what to do.  Do I
unmerge the existing package and install the new one?  My experience
has been mixed.  Sometimes I can unmerge the old package, emerge the
new package, and then re-emerge the old package ... and everything is
happy from the on.  Other times there are some old packages which
still want the old package, other old packages want the new package,
and they can't coexist.

Then we come to the real annoyance,

3. Mozilla vs Seamonkey.  I tried Seamonkey a couple of times, and it
   crashed so often and so quickly that I reverted to mozilla.  Now it
   seems there are quite a few packages which insist on seamonkey and
   are not satisfied with mozilla.

   I use firefox, but I also use mozilla.  Mozilla has a better config
   interface to my tastes.  I may try seamonkey again someday, but
   right now, I don't want seamonkey.

   Why do some packages explicitly care about seamonkey?  Shouldn't
   they be pretty much the same?  Shouldn't the dependencies be happy
   with either one?

   In the meantime, is there some way to convince emerge that
   seamonkey has been installed and to not get its knickers in a
   twist?  I suppose I could always unmerge mozilla, emerge world,
   unmerge seamonkey, and emerge mozilla again, but I get tired of
   having to kick out half a dozen packages like totem, gedit,
   gnome-base, epiphany, etc from the ordinary updates just to get
   them working.

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list