Fwd: [Libjpeg-turbo-users] jpeg-9, API/ABI compatibility, and the future role of this project
Michael Stahl
mstahl at redhat.com
Wed Jan 16 12:02:57 UTC 2013
On 15/01/13 20:04, Xose Vazquez Perez wrote:
> On 01/15/2013 01:01 PM, Adam Tkac wrote:
>
>> Another interesting thread is
>> http://sourceforge.net/mailarchive/message.php?msg_id=30352453
>>
>> We are currently discussing drop of the
>> https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI feature because
>> SmartScale encoding (only reason of the jpeg7 and jpeg 8 ABI bumps) was rejected
>> by ISO and actually doesn't bring any benefit over widely used png/webp codecs.
>>
>> So Fedora will probably stick with old jpeg6 API/ABI unless IJG maintainer
>> reveals some new facts about SmartScale. All facts are currently against
>> SmartScale (image quality/size, compression/decompression speed).
>
> Upstream Tracker shows 0% of binary compatibility with previous
> releases: http://upstream-tracker.org/versions/libjpeg.html
>
> I hope other distributions don't use that release.
FWIW i'm afraid i've had to build jpeg8 from source already to get a
certain binary [1] built on Ubuntu to run on Fedora 17...
[1] actually a git repo full of binaries:
https://wiki.documentfoundation.org/Bibisect
More information about the devel
mailing list