Flatpak: Difference between revisions
Appearance
m link to apparmor |
m add flathub repository |
||
Line 6: | Line 6: | ||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
$ sudo apk add flatpak | $ sudo apk add flatpak | ||
</syntaxhighlight> | |||
== Add Flathub Repository == | |||
<syntaxhighlight lang="shell-session"> | |||
$ sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo | |||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 06:19, 1 April 2022
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. |
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 Flathub (or other Flatpak repositories).
Installation
$ sudo apk add flatpak
Add Flathub Repository
$ sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
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]. Instead, the plan is to bring the sandboxing features to the existing packages with AppArmor.
See also
- postmarketos#18 Evaluating privilege separation for postmarketOS and Alpine apps