--- Begin Message ---
- To: Akira TAGOH <at@gclab.org>
- Subject: Re: Fw: Bug#155689: libgtk2.0-png3: -png3 should Provides: libgtk2.0-0
- From: Owen Taylor <otaylor@redhat.com>
- Date: Sat, 10 Aug 2002 14:44:43 -0400 (EDT)
- Message-id: <20020810184443.5CC3D241D71@fresnel.labs.redhat.com>
- In-reply-to: Akira TAGOH's message of "Sat, 10 Aug 2002 11:35:24 +0900 (JST)"
- References: <20020810.113524.294717087.at@gclab.org>
No, we aren't going to change the soname of GTK+, for any reasons,
for the next 3-4 years.
gdk-pixbuf intentionally does not link directly against libpng
and does not include libpng in the output of:
pkg-config --libs gdk-pixbuf-2.0
So that if an app links only against GTK+, then there is no
problem when the version of libpng changes.
As for the question of apps that link against GTK+-2.0 and
against libpng-1.0 directly ... it's very hard to handle that;
this is why changing sonames is a bad thing. (If you changed the
GTK+ soname, you would generate many more problems like that.)
Possible solutions:
a) Install two copies of the gdk-pixbuf modules, and use a wrapper
script for the application that sets GDK_PIXBUF_MODULEDIR.
b) Hack the GTK+-2.0 gdk-pixbuf not to load the image modules
with RTLD_GLOBAL. (This is what we did for gdk-pixbuf-0.1x
for Red Hat; see the patch in our package.)
I generally wouldn't consider it worth the effort unless you
have actual problems.
Regards,
Owen
(Feel free to forward)
--- End Message ---