seamonkey replaces mozilla?

[Steve Siegfried]

Gang,

This may be re-ringing the same bell, but is seamonkey replacing mozilla?

If so, at least in FC5, if you've already got mozilla and friends
installed, then there doesn't appear to be any upgrade path that doesn't
require deleting mozilla and friends before adding seamonkey.  And from
what I can tell, if you do have mozilla and friends already installed,
you can't get there from here.

In FC5 for example, I've already got installed:
     mozilla-1.7.13-1.1.fc5.i386.rpm
     mozilla-chat-1.7.13-1.1.fc5.i386.rpm
     mozilla-devel-1.7.13-1.1.fc5.i386.rpm
     mozilla-dom-inspector-1.7.13-1.1.fc5.i386.rpm
     mozilla-js-debugger-1.7.13-1.1.fc5.i386.rpm
     mozilla-mail-1.7.13-1.1.fc5.i386.rpm


So trying to install the latest stuff (via yum extender output) I see
stuff like:
     ROOT:root=> yumex
     Mirrordetection : default
     Yum Version : 2.6.1 (/usr/share/yum-cli)
     /usr/lib/python2.4/site-packages/yum/config.py:454: DeprecationWarning: getConfigOption() will go away in a future version of Yum.
     Please access option values as attributes or using getattr().
       DeprecationWarning)
     Loading "installonlyn" plugin
     Repository initialization completed in 32.77 seconds
     Preparing for install/remove/update
     --> Preparing for install
     --> Preparing for remove
     --> Preparing for a partial update
     --> Populating transaction set with selected packages. Please wait.
     ---> Package yelp.i386 0:2.14.3-3.fc5 set to be updated
     ---> Package epiphany.i386 0:2.14.3-3.fc5 set to be updated
     ---> Package devhelp.i386 0:0.11-5.fc5 set to be updated
     ---> Package epiphany-devel.i386 0:2.14.3-3.fc5 set to be updated
     ---> Package devhelp-devel.i386 0:0.11-5.fc5 set to be updated
     ---> Package liferea.i386 0:1.0.24-2.fc5 set to be updated
     ---> Package galeon.i386 0:2.0.3-2.fc5 set to be updated
     --> Running transaction check
     --> Processing Dependency: libxpcom_core.so for package: epiphany
     --> Processing Dependency: seamonkey >= 1.0.7 for package: yelp
     --> Processing Dependency: seamonkey = 1.0.7 for package: liferea
     --> Processing Dependency: seamonkey = 1.0.7 for package: epiphany
     --> Processing Dependency: seamonkey = 1.0.7 for package: devhelp
     --> Processing Dependency: libxpcom_core.so for package: yelp
     --> Processing Dependency: libxpcom_core.so for package: galeon
     --> Processing Dependency: seamonkey-devel >= 1.0.7 for package: epiphany-devel
     --> Processing Dependency: seamonkey = 1.0.7 for package: galeon
     --> Restarting Dependency Resolution with new changes.
     --> Populating transaction set with selected packages. Please wait.
     ---> Package seamonkey-devel.i386 0:1.0.7-0.6.fc5 set to be updated
     ---> Package seamonkey.i386 0:1.0.7-0.6.fc5 set to be updated
     --> Running transaction check
     --> Processing Dependency: mozilla = 37:1.7.13-1.1.fc5 for package: mozilla-js-debugger
     --> Processing Dependency: mozilla = 37:1.7.13-1.1.fc5 for package: mozilla-mail
     --> Processing Dependency: mozilla = 37:1.7.13-1.1.fc5 for package: mozilla-dom-inspector
     --> Processing Dependency: mozilla = 37:1.7.13-1.1.fc5 for package: mozilla-chat
     --> Finished Dependency Resolution

But... when I test removing mozilla and friends via "rpm --test -e",
I get a ton of "XXX is needed by (installed) YYY" errors, some of which
(like gnome-python2-gtkmozembed, libswt3-gtk2, conglomerate and gecko-sharp2)
can't be re-installed because there aren't seamonkey compatible replacements
available.

So unless I'm missing something, there doesn't seem to be a clean upgrade
path from mozilla and friends to seamonkey and friends.

Suggestions are welcome at this point.

-S