Mailinglist Archive: opensuse-factory (648 mails)
| < Previous | Next > |
Re: [opensuse-factory] libjpeg-turbo
- From: Cristian Morales Vega <cmorve69@xxxxxxxx>
- Date: Sun, 7 Nov 2010 22:54:52 +0100
- Message-id: <AANLkTi=T1+dZYmN5nLA=c1Am4MLZv4_YLJ1BJO_wp4j5@xxxxxxxxxxxxxx>
2010/11/7 Pavol Rusnak <prusnak@xxxxxxxxxxxx>:
It's OK with me. So:
- An update is/will be available for 11.3 for bnc#620175. Meaning
libjpeg v6 uses versioned symbols.
- A libjpeg-turbo package is available. Next upstream version will
version symbols. Since they have a history of releasing a new version
every two months I would not bother to patch 1.0.1.
- libjpeg-turbo has a "Colorspace Extensions" that apps could rely on,
and it seems there will be apps linked against libjpeg.so.6 for a long
time and libjpeg-turbo is the only v6 still supported... I don't think
anybody is going to argue about dropping libjpeg6 for 11.4 and use
libjpeg62 (libjpeg-turbo) instead.
What must be still decided is what to do with libjpeg.so.8, knowing that
- It seems libjpeg-turbo will be libjpeg.so.6, by default, for a long time.
- libjpeg-turbo supports the v8 "ABI", but with some features missing
- libjpeg-turbo is a young project (registered in SF on 2010-02-05),
but IJG neither has an history as an active project
- libjpeg.so.6 is what LSB mandates and Fedora uses
Ideally, I would
- Compile against libjpeg62. Fedora and LSB perhaps are not great
causes, but I can't think of even a bad cause to compile against
libjpeg8
- Provide a libjpeg8-devel package from the http://www.ijg.org/ source.
- Provide a libjpeg8 from IJG source and a libjpeg8-turbo*,
conflicting between them. Since IJG will be version "8.x" and
libjpeg-turbo version "1.x" I expect ZYpp to install the IJG version
by default, that would ensure maximum compatibility. If a dev is using
v8 IMHO he is accepting the reduced speed. But if an user wants the
extra speed he could manually install libjpeg8-turbo.
* Not possible until the next upstream release of libjpeg-turbo
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
On 07/11/10 16:40, Cristian Rodríguez wrote:
El 07/11/10 12:09, Cristian Morales Vega escribió:
That "libjpeg62 obsoletes and provides libjpeg8" is probably wrong?
Shouldn't it obsolete/provide libjpeg6?
libjpeg-turbo has a different SONAME, so it SHOULD NOT not conflict, nor
obsolete libjpeg8 in anyway.
jpeg8 must remain installed on the user system on upgrade in case it is
needed by other packages.
Ah, I get it now. Fixed Obsoletes/Provides in my repo, please check if it's
OK :-)
It's OK with me. So:
- An update is/will be available for 11.3 for bnc#620175. Meaning
libjpeg v6 uses versioned symbols.
- A libjpeg-turbo package is available. Next upstream version will
version symbols. Since they have a history of releasing a new version
every two months I would not bother to patch 1.0.1.
- libjpeg-turbo has a "Colorspace Extensions" that apps could rely on,
and it seems there will be apps linked against libjpeg.so.6 for a long
time and libjpeg-turbo is the only v6 still supported... I don't think
anybody is going to argue about dropping libjpeg6 for 11.4 and use
libjpeg62 (libjpeg-turbo) instead.
What must be still decided is what to do with libjpeg.so.8, knowing that
- It seems libjpeg-turbo will be libjpeg.so.6, by default, for a long time.
- libjpeg-turbo supports the v8 "ABI", but with some features missing
- libjpeg-turbo is a young project (registered in SF on 2010-02-05),
but IJG neither has an history as an active project
- libjpeg.so.6 is what LSB mandates and Fedora uses
Ideally, I would
- Compile against libjpeg62. Fedora and LSB perhaps are not great
causes, but I can't think of even a bad cause to compile against
libjpeg8
- Provide a libjpeg8-devel package from the http://www.ijg.org/ source.
- Provide a libjpeg8 from IJG source and a libjpeg8-turbo*,
conflicting between them. Since IJG will be version "8.x" and
libjpeg-turbo version "1.x" I expect ZYpp to install the IJG version
by default, that would ensure maximum compatibility. If a dev is using
v8 IMHO he is accepting the reduced speed. But if an user wants the
extra speed he could manually install libjpeg8-turbo.
* Not possible until the next upstream release of libjpeg-turbo
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |