[Feature]: Desktop app: release packaging (tarball, AppImage)

オープン
#96 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
24/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, linux, rust
領域
desktop, release

調査の方向性

Read the epic #80 first, then the dependencies #81 and #85 and the existing release workflow in release.yml. Check licenses/collect.sh and the desktop workspace packaging inputs described here. Done means a test tag publishes both Linux artifacts, the AppImage runs on the listed distributions, URL handling works, and a branch build is available to the NVIDIA tester.

索引モデルが issue の本文から書いたものです。

説明

enhancement

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a planning session with @PhrolovaMoe. Part of #80, builds on #81 and #85. Read the epic first.

Area

Desktop app

Problem

People need to install the app, and NVIDIA testers need binaries well before the first release, because David's machine is AMD.

Proposed solution
Release artifacts

A desktop job in release.yml (x86_64-unknown-linux-gnu, ubuntu-24.04, GitHub-hosted, glibc), built from the same tag as the server, with --locked:

  • Tarball tinystream-desktop-<version>-x86_64-linux.tar.gz:
    • tinystream-desktop (the binary);
    • dev.tinystream.app.desktop (with MimeType=x-scheme-handler/tinystream;);
    • hicolor icons from assets/logos, at the usual sizes plus scalable;
    • an AppStream dev.tinystream.app.metainfo.xml;
    • LICENSE, README.md, THIRD_PARTY_LICENSES;
    • an install.sh that copies all of that into ~/.local (or a prefix) and runs update-desktop-database.
  • AppImage tinystream-desktop-<version>-x86_64.AppImage, from the same files. The packaging tool (appimagetool or similar) is downloaded at a pinned version and checked against a pinned SHA-256 in the workflow. No unpinned downloads.
  • THIRD_PARTY_LICENSES comes from licenses/collect.sh, extended to take the desktop workspace: its crates (cargo-about over desktop/Cargo.lock), the native stack including mpv/libplacebo/nv-codec-headers (#85), Geist and Lucide.
  • The publish job attaches both to the release, next to the server archives and the APK.
  • aarch64 Linux is left out until there's hardware to test it on.
Dynamic dependencies

Check the final binary with ldd/readelf -d in CI, against an allowlist of libraries every desktop Linux has (glibc, libm, libstdc++, libEGL/libGL, libvulkan, wayland-client/egl/cursor, libxkbcommon, libX11 family, libasound, D-Bus if not pure Rust). Things loaded at runtime (libcuda, libva drivers, PipeWire/Pulse where mpv loads them) aren't in the list. Fail the job on anything else.

Test builds

A workflow_dispatch (and push to feat/desktop) build that uploads the tarball and AppImage as workflow artifacts, so testers can try a branch without a release. It needs no secrets.

Done when

A release from a test tag has both artifacts. The AppImage runs on a clean Ubuntu 24.04, Fedora and Arch (and David's Void). install.sh registers the URL scheme, so xdg-open tinystream://… opens the app. The NVIDIA tester runs a branch build.

主要言語
TypeScript
スター
4
フォーク
1
平均マージ
4時間 49分
マージ済み PR(30日)
5

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

tinystream-dev/tinystream のほかの issue

tinystream-dev/tinystream の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。