jperkin: Have you looked into libvips at all? The Mastodon folks are determined to drop ImageMagick and switch to it.

@pjustice I don't know my image-processing-libraries well enough to know myself. What are the tradeoffs between ImageMagick and libvips ?

I don't really know. The Mastodon team's comments make me think they wanted it because it's faster.

That's a good reason! :)

pjustice: currently blocked by reports.pkgci.org/SmartOS/trunk/x86…609.0356/libjxl-0.11.2nb1/build.log - I'll get gwr's header fixes in which will cover that (pretty sure we were shipping libvips a while back..)

I'm currently learning the hard way that upgrade to masto 4.4 is blocked by some vite / rollup nonsense. Sigh.

Thanks for the vips info.

heh..

i was looking at something and I think it was vite that was ultimately pulling in lightningcss

which requires downloading and running prebuilt binaries

which are built with rust but then run by node.js

like on friday

because it wouldn't build on illumos (because it's missing a prebuilt binary for illumos)

in this masto case, vite is using rollup somehow, possibly indirectly, and rollup doesn't have a native binary for this, and there seems to be no way to insert the override everyone suggests to use @rollup/wasm-node

any tool that doesn't start with the works-everywhere and upgrade-if-possible to some native optimization is just waiting for a tactical nuclear strike. grr.

if I can figure out (haven't really looked at) at the correct incantations to cross-compile rust to produce illumos binaries from a non-illumos platform (IIRC when I've looked in the past, the rust compiler will try to link using the illumos linker which obviously isn't going to work on non-illumos)

i was going to try putting up a PR to create a binary for that at least

since the rust code builds fine on illumos

so if the cross-compiling can work, it hopefully wouldn't be too big a deal to add it

pjustice: I never found a proper way to deal with the rollup mess and in the end just hacked it like this: gist.github.com/wiedi/355dda6590a6f20ee0f7883ae44e726a

thanks for that

I just run mine on debian :/

Damn. Was hoping to point to yours as another one running on smartos when I open the tickets. :)

I got it running on SmartOS back when twitter first imploded but it's something I don't want to spend any time on, so it's one of my ignore-all-the-terrible-things-like-systemd hosts and I try to ignore it as much as possible

m.fru.bar still runs on smartos but I need to look into what it takes to get it up to 4.5 or even the soon to be released 4.6

happy to be tagged in any tickets :D

the most problematic was the issue with hiredis

I did basically the same kind of stunt on hiredis that wiedi does on vite -- rm the .so files rabidly.