Re: Consider to switch libjpeg-turbo as default jpeg

[pin <voidpin%protonmail.com@localhost>]

-------- Ursprungligt meddelande --------
Den 2025-03-18 11:09, Thomas Klausner <wiz%gatalith.at@localhost> skrev:

>  On Tue, Mar 18, 2025 at 10:41:42AM +0100, Robert Bagdan wrote:
>  > The default jpeg implementation is graphics/jpeg in pkgsrc, and
>  > available the graphics/libjpeg-turbo, but for use need to rebuild all
>  > packages that have jpeg dependency.
>  >
>  > It is problem because the most browsers/webengine (firefox, webkitgtk,
>  > chromium, qtwebengine, palemoon) requires libjpeg-turbo, but they
>  > can’t use pkgsrc’s jpeg-turbo, so all build with its own internal
>  > libjpeg-turbo (except the newer webkitgtk in pkgsrc-wip, what is not
>  > ships own libjpeg-turbo).
>  >
>  > As I read the browsers switched to libjpeg-turbo because it is faster,
>  > and has some enhancements compared to libjpeg, which they are using.
>  >
>  > I think switching to libjpeg-turbo as pkgsrc default would be
>  > painless, as libjpeg-turbo has the features of jpeg. When I built
>  > webkitgtk with JPEG_DEFAULT=libjpeg-turbo in /etc/mk.conf, I didn’t
>  > find any issues with the dependencies build.
>  >
>  > What are your opinions?
>  
>  I think this is a good idea.
>  
>  We already have a couple packages in pkgsrc that do not even build
>  against graphics/jpeg, but need libjpeg-turbo, and having ~all web
>  browser agree on that version is a strong sign to use it too.
>   Thomas
>  

FWIW, I have been building all my packages with JPEG_DEFAULT=libjpeg-turbo for sometime and couldn't be more satisfied. I know a few others who are doing the same and haven't heard anything bad.

+1 from me