gtk shared library conflicts (libgtk.so)

[Ray Marshall <ray love vnet net>]

I've just rejoined this list, in the hope that someone can help me
straighten out my system.

System:  RedHat V5.1 with all errata installed.
	 GNOME 0.30 just recently installed

The other day I decided to start using the latest GNOME and its new tools.
I had to upgrade from GNOME 0.13 (from the RedHat 5.1 CD), to GNOME 0.30.
So I picked up all of the .rpm files from gnome and the latest tools that
were there, too.

It turned out that I had install some 0.27 versions, in order to upgrade
to 0.30.  I did that.

UNFORTUNATELY, I just tried to build something that uses libgtk.so, and it
complained about undefined symbols.  That started me looking...

I found that I now have several versions of gtk+ installed.  I spent over
an hour looking for something that might tell me what I am suppose to
have, but no success so far.  Maybe one of you can help.

I have the following RPMs installed:

    gtk+10-1.0.6-1
    gtk+-1.1.1-1
    gtk+-1.1.2-1
    gtk+-1.0.5-2
    gtk+-devel-1.1.2-1

Obviously, I now have multiple versions of a lot of files, and some
strange links.  The first thing I noticed was this:

libgtk.so        --> libgtk-1.1.so.2.0.0  [ RPM: gtk+-1.1.2-1   ]
libgtk.so.1      --> libgtk.so.1.0.6      [ RPM: gtk+10-1.0.6-1 ]
libgtk.so.1.0.5  --------------------	  [ RPM: gtk+-1.0.5-2	]

The longer listing [trimmed so it will fit here] follows:

lib# v libgtk* | grep \.so
         19 Sep 16 12:21 libgtk-1.1.1.so -> libgtk-1.1.so.1.0.0
         19 Sep 16 11:42 libgtk-1.1.so.1 -> libgtk-1.1.so.1.0.0
    1089657 Aug 10 12:29 libgtk-1.1.so.1.0.0
         19 Oct  5 09:38 libgtk-1.1.so.2 -> libgtk-1.1.so.2.0.0
    1120116 Sep 23 12:50 libgtk-1.1.so.2.0.0
         19 Oct  5 09:34 libgtk.so -> libgtk-1.1.so.2.0.0
         15 Oct  5 09:38 libgtk.so.1 -> libgtk.so.1.0.6
     755279 Aug 12 16:42 libgtk.so.1.0.5
     788943 Sep 23 12:12 libgtk.so.1.0.6
lib# 


I NEED HELP!  Is there a single document that says just what I need, and
what I should NOT have installed?


I suspect that there are some other packages that still require older
libraries.  There are just too many interdependencies for me to follow.


This sounds like time for another tool -- one to analyze all dependencies,
in an RPM database, and identified RPMs that are no longer required, or
that can be retired if only one or two other packages are upgraded.

Peace, Love, & Harmony  /  Ray
------------------------------------+------------------------------------
Ray Marshall <raym@vnet.net>        | Unconditional Forgiveness & Love --
Chapel Hill NC or Sutton Mills NH   |   The corner stones of coexistence.
Work: raym@nortel.ca