Template:Flatpak Install

From Kicksecure
Revision as of 03:14, 18 December 2024 by Patrick (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template Content[edit]

Install {{{package}}} via flatpak.

1. Add a Flatpak repository.

A : Kicksecure

===

Kicksecure

Already enabled by default. (system-wide). No additional steps needed to enable the Flathub repository.

B : Kicksecure-Qubes Template

===

Kicksecure-Qubes Template (kicksecure-17)

Already enabled by default. (system-wide). No additional steps needed to enable the Flathub repository.

C : Kicksecure-Qubes App Qube

Kicksecure-Qubes App Qube (kicksecure)

The user needs to Enable the Flathub Repository The Web Archive Onion Version . Must be enabled per-user.

2. Install the flatpak {{{package}}} package.

A : Kicksecure

===

Kicksecure [1]

Click = Copy Copied to clipboard! flatpak install flathub {{{package}}}

B : Kicksecure-Qubes Template

===

Kicksecure-Qubes Template (kicksecure-17) [2]

Note: Advanced users that uninstalled the qubes-core-agent-passwordless-sudo package should see forum thread Warning: Flatpak system operation Deploy not allowed for userarchive.org.

Click = Copy Copied to clipboard! http_proxy=http://127.0.0.1:8082 https_proxy=$http_proxy flatpak install flathub {{{package}}}

C : Kicksecure-Qubes App Qube

Kicksecure-Qubes App Qube (kicksecure) [3]

Click = Copy Copied to clipboard! flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Click = Copy Copied to clipboard! 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[edit]

  1. Kicksecure:
    • system-wide (requires administrative ("root") rights) (compatible with noexec): Click = Copy Copied to clipboard! flatpak install flathub {{{package}}}
    • per-user (no administrative rights required) (probably not compatible with noexec): Click = Copy Copied to clipboard! flatpak --user install flathub {{{package}}}
    What is better? System-wide or per-user?
    • <>usability:</> Flathub is enabled by default system-wide but not per-user.archive.org
    • 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 Kicksecure security improvements user-sysmaint-split. 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.
  2. Kicksecure-Qubes 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 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.
  3. Kicksecure-Qubes 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 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.

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!