Re: libpng conflict?
Chris Cheney <ccheney@cheney.cx> immo vero scripsit:
> This is a really big mess, which extends far beyond just libpng. Imho
> switching everything to use libpng3 in sid is probably the best
> solution overall but it is still a pita. KDE3 is going to use
> libpng3 and has been compiled against it, but at least one KDE app uses
> imlib which needs: 1. all of kde to be compiled against libpng2 2. needs
> a libpng3 version of imlib1 or 3. the app will not be able to be built.
> For everything to work properly in general will require 1. everything to
> be built against old libs indefinitely or 2. rebuild all needed packages
> when new libraries come out... Out of the two options 2. sounds like the
> best option to me.
the imlib package would at least be renamed, and conflict
against old imlib package, if it is going to be recompiled against
libpng3, or alternatively, coordinate with upstream people to
get a new soname.
Debian is probably the only distribution who care about
upgradability between stable releases, and binary-compatibility.
We need to do it.
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/
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: