Bug 6908 - Deleting old GTK shared libraries unacceptable
Summary: Deleting old GTK shared libraries unacceptable
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-libs
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-11-11 03:01 UTC by whitis
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-11-11 15:34:23 UTC

Attachments (Terms of Use)

Description whitis 1999-11-11 03:01:33 UTC
Under the current system, installing gnome from RPMs is
hazardous to your health.  You won't get more than one
GNOME app to work at a time (unless they came in the
same bundle).

This bug report applies to all versions of GTK rpms - even
the old rpms need to be fixed (or a new rpm full of old
versions created).

Redhat loves to delete old versions you still need.  One
place this hurts you is
GTK shared libraries.  The shared library system is smart
enough to
handle multiple library versions simultaneously installed
and will
try to pick the closest match;  Redhat screws this up by
the old ones.  This
is why you can almost never get gnome apps to work.  Every
gnome app
typically needs a different library version (and they aren't
compatible with
other versions because the library calling conventions
stabilized, which would be fine if redhat didn't delete the
old ones).
Every time you install a new gnome app, you need to upgrade
one or
more libaries, which thanks to redhat will break all your
gnome apps.

Comment 1 Michael Fulbright 1999-11-11 15:34:59 UTC
This is not a gnome-libs issue.

Installing the gtk+-1.2-xxx packages will not break existing
applications which are linked against gtk+-1.0. The gtk+10 package,
which is required in order to install the gtk+-1.2 package, has the
required shared libraries which gtk+-1.0 apps require.  The
upgrade to gtk+-1.2 unless the gtk+-1.0 package exists, or you
used --force to install, in which case the consequences are not
guaranteed to be good.

Note You need to log in before you can comment on or make changes to this bug.