Re: Bug#155689: libgtk2.0-png3: -png3 should Provides: libgtk2.0-0
>>>>> On 09 Aug 2002 20:58:46 -0400,
>>>>> "JD" == Joe Drew <hoserhead@woot.net> wrote:
JD> On Fri, 2002-08-09 at 20:47, Akira TAGOH wrote:
>> Hey, libgtk2.0-0png3 isn't really broken the binary
>> compatibility. for example, metacity actually works without
>> rebuild. it was just changing the dependency and to avoid
>> that the programs links both of libpng2 and libpng3 at the
>> same time.
JD> Okay - when will it break binary compatibility? And if it doesn't break
JD> binary compatibility ever, why change the package name?
this answer was described in the above. for example, if a
commercial program as you says links GTK+2.0 and libpng2
*directly*, (and if it is provided as package, then if
libgtk2.0-0png3 provides libgtk2.0-0), it won't works
correctly. anyway those programs needs to be rebuilt.
Note that a file which depends on libpng is not
libg[dt]k-*.so*, it's a loadable module on
/usr/lib/gtk-2.0/2.0.0/loaders.
BTW I have an workaround for people who aren't able to
rebuild them. looking up the module path is able to changes
by GDK_PIXBUF_MODULEDIR. if people can writes a wrapper
script, we may provides the loadable modules only which is
built against libpng2.
>> If we can't provide the GTK+2.0 which is built against
>> libpng2 without conflicts, we have a way only which is
>> waiting a new thing.
JD> What is this way, and what is it waiting on?
new package or release.
--
Akira TAGOH : tagoh@gnome.gr.jp / Japan GNOME Users Group
at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project
: tagoh@redhat.com / Red Hat, Inc.
: tagoh@debian.org / Debian Project
Reply to: