Re: Bug#155689: libgtk2.0-png3: -png3 should Provides: libgtk2.0-0
Joe Drew <hoserhead@woot.net> immo vero scripsit:
> No clue. I've not heard of many gtk, and no gtk2.0.
I will try to present why this method was chosen for GTK2.0:
o Debian was shipping something that was different from everyone else
-- commercial programs will probably ship something that won't run on Debian.
o The only binary incompatiblity would arise if the GTK+ linked application
was directly linked with libpng2.
-- and it would usually be only when user compiles his binary on his
machine, which would mean it would probably be possible to rebuild as well.
(i.e. it is considered not worth the effort to change the soname
= break binary compatibility with every other distribution)
o We want to use the Debian version control system to track our
migration path, to make sure we didn't break anything. (chapter 9)
o (This is a compromise. If we can't get SONAMEs changed in the upstream
level in a reasonable timeframe, we need some work-around.)
regards,
junichi
--
dancer@debian.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
Reply to: