Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Define a way for websites to link to AppImage downloads

未关闭
#1,074 10 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
领域
release

调研方向

首先查阅 AppStream 的 custom-tag 文档以及 KDE 现有的 custom-tag 指南,然后将这些要求与 issue 中描述的 AppImage update-information 字符串进行比较。确定项目应通过 AppStream 提供能够识别渠道的链接,还是重用更新元数据,并记录结果是直接下载,还是不包含硬编码版本的 landing page。

由索引模型根据 Issue 内容生成。

描述

Use case:
https://kde.org/applications/ shows download links for the Windows, Android... app store.
How should AppImages be represented there, and where should the information come from?

The AppStream spec allows specifying URLs to e..g, the application homepage, bugtracker, etc. - but not to, e.g., "the latest AppImage for the stable channel".

Turns out that the AppStream spec allows for custom tags:
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-custom

KDE is already making use of custom tags:
https://community.kde.org/Guidelines_and_HOWTOs/AppStream#KDE_customs_tags
cc
So the question is, do we need/want custom tags for AppImage downloads.

Requirements:

  • The information in the AppStream metainfo file must not hardcode version numbers
  • The information in the AppStream metainfo file should allow for multiple channels (e.g., release, nightly, alpha, beta,..)

Question:

  • Do we want a "deeplink" that results in the AppImage being downloaded, or do we want a link to the download page on which the AppImage can be downloaded by the user?

Food for thought:

  • Do we even need AppStream for this purpose? We could re-use AppImage update information for this purpose. This might completely remove the need for using AppStream to get this kind of information, it is already there and it already supports different channels

@jriddell: AppImage update information is a text string that is embedded within the first few KB of AppImages that support automatic updating (hopefully all of the KDE ones do!). From this string, the URL to the AppImage download can be constructed. Would that be an approach that would be acceptable for this use case, or do you think the information must come from AppStream?

主要语言
没有语言数据
星标
9.5k
派生
586
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AppImage/AppImageKit 的其他 Issue

查看 AppImage/AppImageKit 的全部 Issue

相似的 Issue

更多 Release Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。