@kaia I would’ve said flatpak, but it took OBS Studio an entire 9 months to update their runtime… on their official first party build…
@kaia AppImages or FlatPaks pretty much yea...
Sometimes via a packagemanager (apt, dnf etc.) works but not always.
It's honestly one of the bigger things Linux is lacking in and probs will never really solve.
@finlaydag33k @kaia I don't know how they do it, but Obsidian self-updates within the AppImage, so it's at least possible for that to happen. I don't know how viable it is for other projects to follow suit.
On Arch, I find many more things available through the default and AUR package repositories, so my updates are almost completely through that mechanism. A nice side-effect I hadn't realized before.
@ktneely To my knowledge, AppImages have a "framework" which you can't update and the "app's filesystem" (which the app has free reign in).
Obsidian is an Electron app, so when you press the "update" button in Obsidian, it probably updates the bits getting opened by Electron (maybe Electron itself?), not the AppImage framework.
A downside about the AUR is that you're also always on the bleeding edge, which may not always be desirable and also can lead to dependency hell (which is something that projects like AppImage and FlatPak try to avoid).
@kaia@brotka.st i stopped using meme distros for that reason
@kaia@brotka.st oh it's proprietary no wonder it's not in the main repos :3