Re: Consider to switch libjpeg-turbo as default jpeg

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Thu, Apr 24, 2025 at 05:09:05PM +0000, nia wrote:
> On Thu, Apr 24, 2025 at 04:13:08PM +0200, Thomas Klausner wrote:
> > I've just switched the default to libjpeg-turbo.
> 
> So, fully knowing that it fails to build on a selection of NetBSD
> ports, you did it anyway?

In the discussion, we listed these ports as 'unknown':

earmv4
m68k
mips64eb
mipsel
sh3el
sparc

because we couldn't find binary packages or build logs for them.

Looking at /pub/pkgsrc on ftp.netbsd.org, I now also see:
./packages/NetBSD/m68k/10.0_2024Q4/All/libjpeg-turbo-3.0.4.tgz
./packages/NetBSD/sh3el/10.0_2024Q4/All/libjpeg-turbo-3.0.4.tgz

which leaves four platforms where we are not sure that libjpeg-turbo
builds.  So yes, I decided that if it builds on i386, x86_64, aarch64,
alpha, earmv6hf, earmv7hf, m68k, powerpc, sh3el, sparc64, and even
vax[*], I'm willing to take the gamble that it will also build on the
remaining platforms.

> Great to know how regressions are taken seriously by the leadership
> of this package manager.

You'll have to show a regression first, so far you are just spreading
FUD about them.

> Anyway, I limited it to x86_64 and aarch64 for now. Since people
> want this for chrome...

I'll revert this for now, and if we can find regressions, we can talk
about this again.
 Thomas


[*] looking at Debian binary packages
(https://buildd.debian.org/status/package.php?p=libjpeg-turbo) adds
mips64el, riscv64, hppa, loong64, and sh4 to the list