Consider to switch libjpeg-turbo as default jpeg

[Robert Bagdan <kikadf.01%gmail.com@localhost>]

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?

-- 
Regards,
kikadf