Emil_Shanaty/shacraft-launcher
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: bind AppImage updates to the running bundle

Browse Source
This commit is contained in:
Emil
2026-09-09 20:10:24 +03:00
parent b2ac174398
commit 696c6b0e52
4 changed files with 187 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/updater-release.md
+4 -1
View File
@@ -184,7 +184,10 @@ updates preserve it:
into an appropriate Applications directory before use. A protected destination
may require OS permission or a manual replacement; an installation error never
counts as a completed update.
- Linux x64 AppImage → x64 AppImage at its current writable location. Debian
- Linux x64 AppImage → x64 AppImage at its current writable location. The original
ordinary, non-symlink AppImage must exist, and the frozen Tauri `APPDIR` must
match the running `usr/bin/shacraft-launcher`. Extracted AppDirs and an inherited
environment from another AppImage use manual installation. Debian
packages, RPM, bare development binaries and unsupported architectures never
enter the self-replacement path. Install a new deb through the system package
manager; the launcher does not run privileged package-manager commands.