[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 摘要。