On Tue, Jul 23, 2013 at 02:52:43PM -0700, Don Armstrong wrote: > 1) Does libjpeg-turbo (LJT) now completely support the libjpeg8 ABI?
I think it is more relevant to follow the ABI used by the rest of Linux community. Pretty much everyone but Debian is moving to LJT, most users still using the IJG libjpeg are using it for historic reasons. libjpeg8 ABI is not really a well drafted ABI for long term use, it is libjpeg62b + some new features. Using libjpeg8 ABI as a yardstick of technical readiness feels misguided. Even the IJG itself moved to a new ABI (libjpeg9). > 2) Do we have benchmark results which indicates that LJT is > actually faster than IJG? Some results from Linaro's testing on X86 and ARM: https://wiki.linaro.org/TomGall/LibJpeg8 I think relevant questions for Debian are what is better for Debian users: Fast JPEG encoding and decoding of baseline JPEG images (LJT), or an slower library that is also a development platform for new JPEG image format and ABI features (IJG) ? And how Debian works as part of the wider community: Are the features provided by IJG libjpeg so important, it is worth further fragmenting Linux binary compatibility (most distributions are going LJT) and breaking the universal JPEG image compatibility? Riku -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
