feat: the Flatpak is the Longshot Launcher, the same program as its AppImage #2

Merged
claude merged 1 commit from feat/launcher into main 2026-11-13 17:20:59 -05:00
Collaborator

Why

The Flatpak held Longshot's builder AppImage. Since Longshot dropped the builder UIs, that AppImage has no window, so flatpak run dev.magicbean.Longshot only prints "get the Longshot Launcher". Players use the Longshot Launcher's AppImage, so the Flatpak should be that same program, without the AppImage around it.

What changed

  • dev.magicbean.Longshot.yml: installs the launcher's own program, usr/bin/LongshotLauncher, in /app/bin.
    • It is taken out of the release's signed AppImage at build time and checked with --self-check.
    • Nothing of the AppImage stays or runs: no AppImage runtime, no FUSE.
  • scripts/pick_release.py, config.env: the LongshotLauncher releases (signed with the same key: release_keys.json unchanged apart from its comment).
  • longshot-flatpak.sh: starts the launcher the way the AppImage's AppRun does, with three differences in the environment:
    • XDG_DATA_HOME=~/.local/share. The launcher's home, the game's saves and the shortcuts are where the AppImage puts them, so the AppImage and the Flatpak share them.
    • LONGSHOT_LAUNCHER_EXE is a start script, the same path inside and outside the sandbox, for builder= and the shortcuts.
    • No APPIMAGE, so Flatpak handles the launcher's updates.
  • Network kept (--share=network): the launcher's release checks, downloading Longshot's builder and its tools, crash reports.
  • The desktop entry ("Longshot", as the AppImage's), metainfo and README follow.
  • The workflow's subject says "Longshot Launcher ", and the build checks bin/LongshotLauncher.

Testing

  • pick_release.py against the launcher's releases: v1.0.0-rc.3, SHA256SUMS.sig verified with the pinned key.
  • Without flatpak-builder (not installed here), I tested the same files under org.freedesktop.Platform 26.08 (flatpak build-init + flatpak build):
    • --self-check answers LongshotLauncher v1.0.0-rc.3;
    • the window opens and lists Longshot's releases from git.magicbean.dev, so the network works;
    • longshot-flatpak.sh puts the home in ~/.local/share/longshot/launcher and writes the start scripts.
  • This PR's CI is the first full flatpak-builder build.

Depends on

  • MagicBeanDev/LongshotLauncher: LONGSHOT_LAUNCHER_EXE, and no self-update offer when the launcher isn't started from its own file (branch gab9281/LongshotLauncher:feat/flatpak-path).
  • Until a launcher release has it, the Flatpak's shortcuts point at /app/bin/LongshotLauncher and only work inside the sandbox. Play inside the launcher works.

🤖 Generated with Claude Code

https://claude.ai/code/session_015KgSKoUqUvce5UXG89NBgi

## Why The Flatpak held Longshot's builder AppImage. Since Longshot dropped the builder UIs, that AppImage has no window, so `flatpak run dev.magicbean.Longshot` only prints "get the Longshot Launcher". Players use the Longshot Launcher's AppImage, so the Flatpak should be that same program, without the AppImage around it. ## What changed - `dev.magicbean.Longshot.yml`: installs the launcher's own program, `usr/bin/LongshotLauncher`, in `/app/bin`. - It is taken out of the release's signed AppImage at build time and checked with `--self-check`. - Nothing of the AppImage stays or runs: no AppImage runtime, no FUSE. - `scripts/pick_release.py`, `config.env`: the LongshotLauncher releases (signed with the same key: `release_keys.json` unchanged apart from its comment). - `longshot-flatpak.sh`: starts the launcher the way the AppImage's `AppRun` does, with three differences in the environment: - `XDG_DATA_HOME=~/.local/share`. The launcher's home, the game's saves and the shortcuts are where the AppImage puts them, so the AppImage and the Flatpak share them. - `LONGSHOT_LAUNCHER_EXE` is a start script, the same path inside and outside the sandbox, for `builder=` and the shortcuts. - No `APPIMAGE`, so Flatpak handles the launcher's updates. - Network kept (`--share=network`): the launcher's release checks, downloading Longshot's builder and its tools, crash reports. - The desktop entry ("Longshot", as the AppImage's), metainfo and README follow. - The workflow's subject says "Longshot Launcher <tag>", and the build checks `bin/LongshotLauncher`. ## Testing - `pick_release.py` against the launcher's releases: v1.0.0-rc.3, `SHA256SUMS.sig` verified with the pinned key. - Without `flatpak-builder` (not installed here), I tested the same files under org.freedesktop.Platform 26.08 (`flatpak build-init` + `flatpak build`): - `--self-check` answers `LongshotLauncher v1.0.0-rc.3`; - the window opens and lists Longshot's releases from git.magicbean.dev, so the network works; - `longshot-flatpak.sh` puts the home in `~/.local/share/longshot/launcher` and writes the start scripts. - This PR's CI is the first full `flatpak-builder` build. ## Depends on - MagicBeanDev/LongshotLauncher: `LONGSHOT_LAUNCHER_EXE`, and no self-update offer when the launcher isn't started from its own file (branch `gab9281/LongshotLauncher:feat/flatpak-path`). - Until a launcher release has it, the Flatpak's shortcuts point at `/app/bin/LongshotLauncher` and only work inside the sandbox. Play inside the launcher works. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_015KgSKoUqUvce5UXG89NBgi
feat: the Flatpak is the Longshot Launcher, the same program as its AppImage
All checks were successful
Longshot Flatpak / flatpak (pull_request) Successful in 2m23s
68a1c4792f
The Flatpak held Longshot's builder AppImage, which has no window since
Longshot dropped the builder UIs: players use the Longshot Launcher. It
now installs the launcher's own program (usr/bin/LongshotLauncher, taken
out of the release's signed AppImage at build time and self-checked) in
/app/bin. Nothing of the AppImage runs: no AppImage runtime, no FUSE.

- pick_release.py and config.env: the launcher's releases (the same
  signing key).
- longshot-flatpak.sh: the AppImage's places (XDG_DATA_HOME =
  ~/.local/share: the same home, saves and shortcuts), the start script
  as LONGSHOT_LAUNCHER_EXE, no APPIMAGE (Flatpak updates it).
- Network kept: the launcher's release checks and downloads.
- The desktop entry and metainfo say the launcher; README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015KgSKoUqUvce5UXG89NBgi
claude merged commit 3a6c76a963 into main 2026-11-13 17:20:59 -05:00
claude deleted branch feat/launcher 2026-11-13 17:20:59 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBean-Mirror/longshot-flatpak-builder!2
No description provided.