Repository navigation
Conversation
|
Hi @lcestou, thanks for your submission. One question though: |
|
No. Upkeep downloads the whole AppImage from the release, then swaps it in after keeping the old one as a restore point. It reads the embedded update information only when you add an app, to find the project's repo. I did look at zsync. Only about 200 of the 1,825 AppImages in the catalogue publish a Since the other Updaters entries all implement AppImage update, would Upkeep fit better under Package managers? It also updates archives, .deb/.rpm and other kinds, so it's closer to bauh or AppMan. Happy to move the line. |
Adds Upkeep at the bottom of Updaters.
How it differs from the updaters already listed: it does not need update information inside the AppImage. It reads the app's releases on GitHub, GitLab or Codeberg, picks the AppImage by a pattern, and swaps it in place, keeping the file's name and mode. Before each update it keeps the old AppImage as a restore point, runs the new one to read its version, and puts the old one back if that fails. It is a tray app with one list, and ships tested entries for 1,825 AppImages.
Tested on Linux Mint 22 and in Ubuntu 26.04, Debian 13, Fedora 45, AlmaLinux, Arch and openSUSE VMs; documented in the repo's README and docs/. GPL-3.0-or-later.