I use Arch btw
Sister communities:
Community rules
Please report posts and comments that break these rules!
I just distribute it as a self-contained executable/archive. ¯\_(ツ)_/¯
Valid solution, but I miss unified updates with appimages and such
Yeah, that's the fun part. Hooking into some auto-update mechanism would be useful to me.
But my stuff is mostly in the scratching-my-own-itch stage, so setting up a FlatHub account, Flatpak metadata, sandbox rules, probably an icon and screenshots and whatnot, and automating the build+releases, just to get auto-updates, yeah... no.
I could code a whole nother project in the time that would take.
As long as your application is statically linked, I don't see any issue with that.
So, like, dumb question. People here assumed that I mean AppImages, whereas I actually meant just a statically linked binary. Is that really the only reason why AppImage exists? So, that dynamically linked applications can be distributed like statically linked ones?
You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia's or mesa's opengl?
The majority of AppImages I've seen have been dynamically linked, yes. But it's also used for packaging assets.
Nix: you package it yourself and do a pull request
Sadly, many flatpaks don't even work on NixOS properly because of assumptions about the file structure or similar