To stay properly updated and keep any unnecessary surprise out of the equation, #Beeper better have their #flatpak published (on #Flathub)! Sorry, but AppImage isn't enough.
"Update" itself by removing original AppImage file and placing a fresh version in the same directory.
And that's why I insist on packaging with #Flatpak (by far, just universal way on Linux) or distro formats! Shortcuts to #Beeper and some other apps just keep breaking and breaking, because, when you press "Update" inside the app, it keeps doing such intrusive stuff. Years were put into improving package management just to avoid doing this same mistake. Come on now, don't reinvent the updates.
@vintprox we need to make #Linux programs packaged in #Flatpak have a universal alert (which can be disabled) for updates, where if the program has an update, it will give you a button to the Flatpak store (like some android apps).
@HoseanRC It's like "Check for updates" in an application, but natively? I dig that idea.
Doesn't hurt to check system updates, among which our packaged app may take place. But, being bombarded daily with weird ones, I understand why it's easy to skip a new release of your favorite program.
@vintprox some times apps need to be on the latest version, it's ok to inform the user about the update before updating (unlike #Beeper where auto updates can't be disabled).
Check for updates on distro repos is hard, because of local package indexing, and it will take lot of time on slow Internet speeds.
But for #Flatpaks it's much better since #Flatpak servers index the packages, so it's easy to get the update info in a single request.
Auto update check on startup is easy and good on Flatpaks.
Add comment