I've spent the most part of today getting rid of Mac OS X on my Mac Pro, which was occupying two disks in mirrored RAID, for good, and installing Void… on ZFS!
And now, when I'm almost there — at least I can run Lagrange under Sway, I attempt to install my carefully crafted Firefox 124 without WebPee support and come to a painful realisation: "Architecture not supported"😱
Damn, I always forget not only the fact that GLibC flavour of Void exists, but that e.g. x86_64 without -musc is IT!!!🤬
@m0xee so im all for removing unwanted deps, but why no webp support?
@trdebunked
I have a pretty severe case of allergy to all things Google and prefer to have as little in my system as possible, besides I don't see the point in either it or VP9 when JPEG XL and AV1 exist already. Here is a more elaborate answer in case you're interested: https://Breloma.m0xEE.Net/objects/988ae23c-f5d4-4408-9aae-bb769e16099b
@m0xee id like to get rid of google too, but while i dont technically need webp for anything im less likely to eliminate youtube (frontends- i dont even know what youtube.com looks like at this point) or webm, so webp seems like a battle hardly worth fighting. still, i really meant it when i said im all for removing unwanted deps. i wish more people would try. it would help monopolies less.
@trdebunked
And in fact, I didn't get rid of the dependency entirely — they have libwebp in-tree and they didn't make it easy to disable it at build time even, that would require quite a bit more work. I just undid the commit that made it non-optional and brought back the image.webp.enabled preference. Essentially, the code is still there, it just lays dormant.