Ship install.sh with the Linux tarball

[JoshuaLampert]

The .tar.gz already carried a .desktop file and an icon, and neither worked where it was unpacked: Exec= is a bare command name and Icon= a theme lookup. Unpacking and running ./pappus was fine; putting the app in the menu meant knowing where those two belong.

What changes

• linux/packaging/install.sh copies the folder to ~/.local/opt/<app id>, writes the desktop entry into ~/.local/share/applications with an absolute Exec=, puts the icon into the hicolor theme, and links ~/.local/bin/pappus. uninstall.sh removes exactly those, and its symlink only while it still points into its own install.
  • The absolute Exec= because ~/.local/bin is not on every distribution's PATH, and never on the session's PATH when that directory is created after login.
  • ~/.local/opt/<app id> and not ~/.local/share/<app id>, which is where path_provider keeps that build's preferences.
  • The entry is packed as a template, <app id>.desktop.in, not as a .desktop file. Shipped ready-made, it was the file a file manager offers as a launcher, and dragged onto a desktop it failed with "pappus: command not found".
  • Everything is derived from that template, so the CI build installs beside the released app, under the command name pappus-ci.
  • POSIX sh, no root, nothing outside $HOME.
• tool/package_linux.sh puts both scripts in the tarball, and now refuses to package a bundle built as the other build: the application id is compiled into the executable, so it is read back with strings instead of taken on trust from the environment. Setting PAPPUS_SIDE_BY_SIDE for the build and forgetting it for the packaging is otherwise silent and produces a CI build wearing the released app's name, entry and icon. That is how this was found.
• Docs: README, CHANGELOG, AGENTS.md.

Verified, in a throwaway HOME

• ./install.sh created all four paths and rewrote Exec= to the absolute path.
• Starting the app through the installed entry's Exec= worked from an unrelated working directory.
• ./uninstall.sh left nothing behind but the app's own data directory, which it must not touch.
• The new guard fails with the mismatched bundle and passes with a matching one, in both directions.

Verified on a real desktop

• "Pappus CI" appears in the application menu and starts from there. The icon shows after logging in again.
• The installed entry copied onto the desktop starts the app.
• uninstall.sh removes the program, the command, the menu entry and the icon, and keeps the settings and the database.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!