Proposal: add a Flatpak packager

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
build-system

调研方向

Read the AppImage and DEB packager structures mentioned in the proposal to understand how NBPackage organizes packagers. Check how package.runtime and image-only behavior are handled there, then compare the proposed flatpak-builder flow and options with the existing design. Done means the maintainers agree on the approach and scope before implementation begins.

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

描述

Hi,
I would like to add Flatpak support to NBPackage, as a new packager type linux-flatpak. Before I write any code, I want to ask if you are interested in this feature, and if the design below is OK for you.

Idea

  • A new package org.apache.netbeans.nbpackage.flatpak, with the same structure as the AppImage and DEB packagers.
  • The image is a flatpak-builder project folder: a YAML manifest, the application files, a .desktop file, a metainfo file and icons. With --image-only, users get a manifest they can edit.
  • The package step runs flatpak-builder --repo and then flatpak build-bundle, to create a single .flatpak file.
  • Java: the JDK from package.runtime is copied to /app/jdk. If no runtime is set, the user can choose an OpenJDK SDK extension instead.
  • New options, for example package.flatpak.app-id (required), runtime and SDK version, and finish-args (sandbox permissions).

Why
NetBeans is already on Flathub (flathub/org.apache.netbeans), but that manifest is maintained outside the project and only covers the IDE. With a packager in NBPackage, platform (RCP) applications could also be packaged as Flatpak, with the same tool and configuration as the other formats. For example, the jMonkeyEngine SDK already uses NBPackage to build its DEB, Windows and macOS installers. A linux-flatpak packager would let projects like this publish a Flatpak with the same configuration.

Questions

  1. Are you interested in this feature?
  2. Is this design OK, or do you prefer a different approach (for example flatpak build-init / build-finish directly, without flatpak-builder)?
  3. Is it OK to install flatpak and flatpak-builder in the Linux CI job?

If you agree, I can open a first PR with the packager, unit tests and README changes, and a second PR for CI.

Thanks!

主要语言
Java
星标
35
派生
13
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

apache/netbeans-nbpackage 的其他 Issue

查看 apache/netbeans-nbpackage 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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