request: organize prerequisites
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- linux
调研方向
Start by reviewing the official AppImage documentation referenced by the issue and the linked gist. Identify where it describes runtime and build prerequisites, then clarify the required packages and container permissions there. Done means the documentation explains common dependencies and limitations of standalone AppImages; the requested distro package bundles would need separate implementation work.
由索引模型根据 Issue 内容生成。
描述
AppImage executables are often not, in fact standalone. Especially in a container context.
At a minimum, building and running AppImage's seem to require:
- OS packages: appstream, appstream-util, ca-certificates, curl, file, fuse, gpg
--device /dev/fuseand--cap-add SYS_ADMINsupplied todocker runcommands
The AppImage runtime should be included with appimagetool, instead of generating expensive network traffic (ca-certificates, curl).
OS packages commonly needed to run AppImages, should be bundled into conventional OS packages. For example, a simple "appimage" Debian package that requires the file and fuse packages. fuse may be marked optional. Likewise for Alpine, RHEL, Slackware, and other distros.
OS packages commonly needed to build AppImages, should be bundled into conventional OS packages. For example, a simple "appimage-dev" Debian package that requires the appstream, appstream-util, and appimage packages. Likewise for Alpine, RHEL, Slackware, and other distros.
https://gist.github.com/mcandre/22e52940c2f6850cfb575455f904402e
Sometimes, an AppImage is able to generate some kind of useful message about missing components on launch. Other times, the AppImage fails at execve, with generic execution errors. Official AppImage documentation should clarify common requirements, instead of insisting that these are standalone applications. Modern Linux environments frequently omit even basic tools like file in order to reduce attack surface, reduce operating costs, and so on.
- 主要语言
- 没有语言数据
- 星标
- 9.5k
- 派生
- 586
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AppImage/AppImageKit 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
AppImage/AppImageKit#1428 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 68/100
AppImage/AppImageKit#1164 · 2 条评论 · 1 个 reaction ·
-
难度 3/5 1-2 天 新手友好度 62/100
AppImage/AppImageKit#1450 ·
-
难度 4/5 3-5 天 新手友好度 48/100
AppImage/AppImageKit#1435 · 2 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
AppImage/AppImageKit#1434 · 2 条评论 ·
查看 AppImage/AppImageKit 的全部 Issue
相似的 Issue
-
bug cli p3
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
components-web-app/docs#297 ·
-
documentation
难度 1/5 1-3 小时 新手友好度 82/100
topoteretes/cognee#6239 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
w3c/vc-barcodes#75 ·
-
area:terraform priority:low source:reader type:enhancement
难度 2/5 1-3 小时 新手友好度 65/100
stephrobert/blog-roadmap#104 ·