{{Header}}
__TOC__
= Template Content =
Install {{{package}}}
via [[Install_Software#Flatpak|flatpak]].
{{Box|text=
'''1.''' Add a Flatpak repository.
{{flatpak_add_repository_short}}
'''2.''' Install the flatpak {{{package}}}
package.
{{Tab
|type=controller
|content=
{{Tab
|type=section
|linkid=os-nonqubes
|active=true
|image=[[File:Kicksecure-logo-icon.svg]]
|title={{Headline|h=3|content=A : {{non_q_project_name_short}}}} ===
|content=
{{non_q_project_name_short}} [
{{non_q_project_name_short}}:
* system-wide (requires [[root|administrative ("root") rights]]) (compatible with [[noexec]]): {{CodeSelect|code=
flatpak install flathub {{{package}}}
}}
* per-user (no administrative rights required) (probably not compatible with [[noexec]]): {{CodeSelect|code=
flatpak --user install flathub {{{package}}}
}}
What is better? System-wide or per-user?
* <>usability:> [https://forums.whonix.org/t/flatpak-as-a-software-source-flathub-as-a-source-of-software/8500/61 Flathub is enabled by default system-wide but not per-user.]
* multi-user: On a multi-user system (probably if multiple human users use the same computer, which is rare nowadays), system-wide might be preferable as this saves disk space.
* At preset: Does not make any difference.
* Future-proof: Per-user might be more future-proof. It would be compatible with future {{project_name_short}} security improvements [[Dev/boot_modes]] (strong user account isolation). However, [[noexec]] for the home folder is to be considered later, at which point this documentation needs to be updated once that has been implemented.
]
{{CodeSelect|code=
flatpak install flathub {{{package}}}
}}
}}
{{Tab
|type=section
|linkid=os-qubes-template
|image=[[File:Qubes-logo-blue.png]]
|title={{Headline|h=3|content=B : {{q_project_name_short}} Template}} ===
|content=
{{q_project_name_short}} Template ({{project_name_workstation_template}}
) [
{{q_project_name_short}} Template: ]flatpak
cannot be used with the --user
option. This is because in case of using a Qubes Template, the flatpak needs to be installed system-wide into the /var/lib/flatpak
folder. This is due to [[Qubes#Qubes_Persistence|Qubes Persistence]]. If the --user
option was used, the flatpak would only be available in the Template's home folder but not in any App Qube based on that Template, because App Qubes have their own independent home folder.
Note: Advanced users that uninstalled the qubes-core-agent-passwordless-sudo
package should see forum thread [https://forums.whonix.org/t/warning-flatpak-system-operation-deploy-not-allowed-for-user/20393 Warning: Flatpak system operation Deploy not allowed for user].
{{CodeSelect|code=
http_proxy=http://127.0.0.1:8082 https_proxy=$http_proxy flatpak install flathub {{{package}}}
}}
}}
{{Tab
|type=section
|linkid=os-qubes-appqube
|image=[[File:Qubes-logo-blue.png]]
|title={{Headline|h=3|content=C : {{q_project_name_short}} App Qube}}
|content=
{{q_project_name_short}} App Qube ({{project_name_workstation_vm}}
) [
{{q_project_name_short}} App Qube: ]flatpak
should be used with the --user
option. This is because in case of using an App Qube, the flatpak needs to be installed per-user only into the ~/.local/share/flatpak
folder and not system-wide. This is due to [[Qubes#Qubes_Persistence|Qubes Persistence]]. If the --user
option was not used, the flatpak would only be available in the App Qube's non-persistent /var/lib/flatpak
folder located in the root image.
{{CodeSelect|code=
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
}}
{{CodeSelect|code=
flatpak --user install flathub {{{package}}}
}}
}}
}}
'''3.''' Done.
The procedure of installing {{{package}}}
is complete.
'''4.''' Upgrades notice.
Note: this procedure will not keep the software up-to-date. How to update installation installed by flatpak is also documented on the [[Operating System Software and Updates]] wiki page.
}}
= Footnotes =
{{Footer}}
[[Category:MultiWiki]]