Is it fair to consider that Linux users are generally out of luck if they don’t use rpm/deb based distros now that the AppImage is gone?
I’ll describe my adventures.
Downloaded https://github.com/BurningTreeC/tiddlydesktop-rs/releases/download/v0.0.37/tiddlydesktop-rs-0.0.37-1-x86_64.pkg.tar.zst , extracted things, ran the binary
./tiddlydesktop-rs
./tiddlydesktop-rs: error while loading shared libraries: libwebkit2gtk-4.1.so.0: cannot open shared object file: No such file
or directory
I have a libwebkit2gtk-4.0.so file in my Slackware64 -current (15.0+) system. I went and created a symlink, albeit it’s a bad idea to do it like this.
./tiddlydesktop-rs
./tiddlydesktop-rs: error while loading shared libraries: libjavascriptcoregtk-4.1.so.0: cannot open shared object file: No such file or directory
Same.
./tiddlydesktop-rs
(process:5664): libsoup-ERROR **: 17:11:27.455: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Trace/breakpoint trap ./tiddlydesktop-rs
Full stop this time. I don’t know how to proceed further.
Since I’m AppImage illiterate (in terms of how it works), it’s probably not worth for you to elaborate on your decision why it is gone, since I won’t understand anyway. But from a strictly end user point of view, an AppImage is clearly handy - just one file to download, all dependencies included (so the situation above should never happen), make it executable and run it. Not to mention the selfish and mercantile end user argument “how come there are AppImages for many programs but not for this one”.
As for building from source, I don’t know if it’s worth trying on old hardware.