Proposal: add a Flatpak packager

Aperta
  • Qualcosa non va?
#149 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
build-system

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
Java
Stelle
35
Fork
13
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/netbeans-nbpackage

Tutte le issue di apache/netbeans-nbpackage

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.