Edit history

When a user installs Fluxer through a .tar.gz archive and an update appears, the user is prompted to manually download, extract and replace the Fluxer install, when the client could very well do this by itself.

The OS (and probably the app itself too) is aware where the fluxer binary was launched from. When an update is prompted, it should just start downloading the new archive to that directory, extract it overwriting the old one, and relaunch the app. x86@uefi-pc ~ $ pgrep -a fluxer 64983 /home/x86/.app/Fluxer-2026.1004.13532-linux-x64/fluxer pgrep is a standard UNIX utility so it's present on all Linux distributions pretty much (+ on the dozen other Unix and Unix-like OSes). There are other distro-agnostic ways of getting this information too such as using the "readlink" command.

When a user installs Fluxer through a .tar.gz archive and an update appears, the user is prompted to manually download, extract and replace the Fluxer install, when the client could very well do this by itself.

The OS is aware where the fluxer binary was launched from. When an update is prompted, it should just start downloading the new archive to that directory, extract it overwriting the old one, and relaunch the app. x86@uefi-pc ~ $ pgrep -a fluxer 64983 /home/x86/.app/Fluxer-2026.1004.13532-linux-x64/fluxer pgrep is a standard UNIX utility so it's present on all Linux distributions pretty much (+ on the dozen other Unix and Unix-like OSes). There are other distro-agnostic ways of getting this information too such as using the "readlink" command.