CommandCodeAI / CommandCodeAI/desktop

[Feedback]: Add an official RPM package for RPM-based Linux distributions

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

@aliarain 已经在做这个了。

开始于 2026年9月7日。

enhancement
主要语言
Shell
星标
80
派生
2
PR 合并指标
30 天内没有已合并 PR

描述

What problem are you trying to solve?

Command Code currently provides a .deb package and an AppImage for Linux, but there is no official .rpm package.

This makes installation and application lifecycle management less convenient on RPM-based distributions such as Fedora, RHEL, CentOS Stream, Rocky Linux, AlmaLinux, and openSUSE.

Although the AppImage can be used as a workaround, it does not provide the same native package-manager integration as an RPM package, including installation, upgrades, removal, dependency management, and managed deployment through tools such as dnf, yum, or zypper.

What would improve it?

Please publish an official x86_64 RPM package with each GitHub release, alongside the existing .deb and AppImage artifacts.

For example:

CommandCode-<version>-1.x86_64.rpm

Ideally, the RPM package should:

  • Install the application in a standard system location.
  • Install the application icon and .desktop entry.
  • Declare the required runtime dependencies.
  • Support clean installation, upgrades, and removal using dnf or rpm.
  • Be included in the project's release checksums or provenance information.
  • Be detected and installed by install.sh on supported RPM-based distributions.
  • Be tested at least on a currently supported Fedora release.

ARM64 RPM support could be added separately if Linux ARM64 builds become available.

What do you do today?

I currently have to download and manage the AppImage manually.

The existing .deb package cannot be installed natively on my RPM-based Linux distribution, and converting the Debian package with third-party tools is not a reliable or officially supported solution.

Product area

Installation and updates

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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