Re: Consider to switch libjpeg-turbo as default jpeg

[nia <nia%NetBSD.org@localhost>]

On Tue, Mar 18, 2025 at 05:39:56PM +0100, Robert Bagdan wrote:
> > I see that we currently do not have packages for libjpeg-turbo (but for jpeg) for:
> >
> > earmv4
> > m68k
> > mips64eb
> > mipsel
> > sh3el
> > sparc
> >
> 
> In theory:
> Because for these archs browsers aren't available, is it possible to
> keep default jpeg
> on ports where libjpeg-turbo is not available?
> Or this would be complicated?

Firefox, Pale Moon, etc, all support building with their own internal copy
of the jpeg library. This might actually be preferrable in some
circumstances - the browsers have requirements (sse? avx?) that the rest of
the package tree doesn't. In the past, Mozilla have made modifications
to their vendored libraries that make building with the system library
unstable unless their own patches are applied.

The chromium package is a complete mess that should have never
been comitted, so no comment there.