Jump to content

Flatpak: Difference between revisions

From postmarketOS Wiki
m Changed 1 letter
 
(7 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{note|postmarketOS and Alpine developers have no control over the Flatpak repositories and the software may not follow the same [[About_postmarketOS#Principles|principles]] as we do. Flathub has proprietary software in their repositories.}}
[https://flatpak.org Flatpak] is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.


The recommended way of installing applications in postmarketOS is through the official package repositories from Alpine and pmOS. Advanced users may consider installing Flatpak to install additional applications from [https://flathub.org Flathub] (or other Flatpak repositories).
postmarketOS supports installing Flatpaks, similar to installing packages from the official Alpine repositories.


== Installation ==
== Installation ==
<syntaxhighlight lang="shell-session">
$ sudo apk add flatpak
</syntaxhighlight>


== Add Flathub Repository ==
Install {{pmaport|postmarketos-base-ui-flatpak}} (if not already) to install Flatpak and configure Flathub as a system-level flatpak repo.
<syntaxhighlight lang="shell-session">
 
$ sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
{{note|postmarketOS and Alpine developers have no control over the Flatpak repositories and the software may not follow the same [[About_postmarketOS#Principles|principles]] as we do. Flathub has proprietary software in their repositories.}}
</syntaxhighlight>
 
=== Application management ===
 
To manage applications and repositories of Flatpak, you can use {{aport|gnome-software}} or {{aport|discover}}.


== Why there is no postmarketOS-specific Flatpak repository ==
== Why there is no postmarketOS-specific Flatpak repository ==
Flatpak has good sandboxing features. However, the packaging format is entirely different to APKBUILD, in syntax and in its philosophy. If we created our own Flatpak repository, we would have much more maintenance effort [https://gitlab.com/postmarketOS/postmarketos/-/issues/18#flatpak]. Instead, the plan is to bring the sandboxing features to the existing packages, see {{issue|1596|pmaports}}.
Flatpak has good sandboxing features. However, the packaging format is entirely different to APKBUILD, in syntax and in its philosophy. If we created our own Flatpak repository, we would have much more maintenance effort [https://gitlab.postmarketos.org/postmarketOS/postmarketos/-/issues/18#flatpak].


== See also ==
== See also ==
* {{issue|18|postmarketos}} Evaluating privilege separation for postmarketOS and Alpine apps
* {{issue|18|postmarketos}} Evaluating privilege separation for postmarketOS and Alpine apps
* [https://wiki.archlinux.org/title/Flatpak Flatpak - ArchWiki]
[[Category:Apps]]

Latest revision as of 00:33, 5 February 2025

Flatpak is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.

postmarketOS supports installing Flatpaks, similar to installing packages from the official Alpine repositories.

Installation

Install postmarketos-base-ui-flatpakPMOS (if not already) to install Flatpak and configure Flathub as a system-level flatpak repo.

Note postmarketOS and Alpine developers have no control over the Flatpak repositories and the software may not follow the same principles as we do. Flathub has proprietary software in their repositories.

Application management

To manage applications and repositories of Flatpak, you can use gnome-software or discover.

Why there is no postmarketOS-specific Flatpak repository

Flatpak has good sandboxing features. However, the packaging format is entirely different to APKBUILD, in syntax and in its philosophy. If we created our own Flatpak repository, we would have much more maintenance effort [1].

See also