Re: Bug#155689: libgtk2.0-png3: -png3 should Provides: libgtk2.0-0
On Wed, 2002-08-07 at 05:19, Torsten Landschoff wrote:
> But what is the other solution? Surely there must be a soname change
> in some way. In any case I think png3 is the way to go.
Insofar as libpng3 is a good library, I agree.
However, I have seen no evidence that making libgtk2.0-0png3 the
"default" gtk for Debian is a good idea. It provides no benefit to
users, as libpng3's different and greater abilities are not taken
advantage of in gtk2.0, and it does offer some serious disadvantages.
Consider the following situation:
User installs Woody. User has a locally compiled version of foo 1.0,
linked against Woody's libgtk2.0-0.
User upgrades to sarge.
User now has the choice of: use foo, or use everything else that uses
gtk2.0 and is in debian, as -0png3 Conflicts with -0.
You might say "recompile foo," but what if foo is a commercial program?
What if foo has released foo 2.0, which is entirely incompatible with
foo 1.0, the user doesn't want to run foo 2.0, and the user can't find
foo 1.0's sources anymore?
I don't think it's responsible to make libpng3 the default for gtk2.0
after we've released a libpng2-linked version of gtk2.0 into stable.
Surely, waiting for gtk2.[12] and THEN transitioning would be a better
idea.
Or, am I missing something?
--
Joe Drew <hoserhead@woot.net> <drew@debian.org>
"This particular group of cats is mostly self-herding." -- Bdale Garbee
Reply to: