Re: JPEG 8 transition
On 2010-02-14, Marc 'HE' Brockschmidt <firstname.lastname@example.org> wrote:
> I think we might even do this before releazing squeeze. Once we have
> versioned symbols, the transition won't hurt as much.
> The current situation is quite problematic, as we can't foresee how many
> package can break after partial upgrades. We know at least of one issue
> when kdm loads both libjpeg62 and libjpeg8, but there will probably
> dozens of other problems.
I wrote a couple of lines yesterday on irc that no matter what we do
that involves libjpeg8, it will break running lsb GUI apps.
A lsb app is expected to be able to use system libraries of Qt or GTK
and libjpeg62 and is built against a libjpeg without versioned symbols.
The system libraries of GTK or Qt has plugins to pull in system libjpeg,
which then will load libjpeg when the library's image routines is used for
a jpeg image.
If GTK or Qt is using libjpeg8 for jpeg handling, we have the disaster.
The more I look into this, the more it looks like libjpeg is a library
that can never ever change SONAME, until it from upstream side is symbol
versioned *and* the versioned symbols is written into LSB.