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

未關閉
#96 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
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 分鐘
30 天內合併 PR
5

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

tinystream-dev/tinystream 的其他 Issue

查看 tinystream-dev/tinystream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。