Flatpak: Difference between revisions
Emulate Flatpaks different architecture |
m enhance: links |
||
(21 intermediate revisions by 6 users not shown) | |||
Line 3: | Line 3: | ||
This article extends the documentation in the [https://nixos.org/manual/nixos/stable/#module-services-flatpak NixOS manual]. | This article extends the documentation in the [https://nixos.org/manual/nixos/stable/#module-services-flatpak NixOS manual]. | ||
== | == Installation == | ||
=== Global === | |||
Using this configuration, <code>flatpak</code> will be installed and ready to use globally for all users: | Using this configuration, <code>flatpak</code> will be installed and ready to use globally for all users: | ||
{{file|/etc/nixos/configuration.nix|nix | {{file|3=services.flatpak.enable = true;|name=/etc/nixos/configuration.nix|lang=nix}} | ||
=== Per-User === | |||
</ | If you'd rather make Flatpak available to a specific user, add <code>flatpak</code> to that user's packages | ||
{{file|3=users.users."user" = { | |||
{{file| | |||
packages = with pkgs; [ | packages = with pkgs; [ | ||
flatpak | flatpak | ||
]; | ]; | ||
}; | };|name=/etc/nixos/configuration.nix|lang=nix}} | ||
=== Window Managers / Compositors Patches === | |||
After adding the desired solution to your configuration file, Flatpak will be installed, but it is not always added to your path directly, e.g. when you are using Sway. | After adding the desired solution to your configuration file, Flatpak will be installed, but it is not always added to your path directly, e.g. when you are using Sway. | ||
To manually add it to the path while using the [[Greetd]] login manager and [[Sway]], create a <code>.profile</code> file with an override for your <code>XDG_DATA_DIRS</code> path, e.g.: | To manually add it to the path while using the [[Greetd]] login manager and [[Sway]], create a <code>.profile</code> file with an override for your <code>XDG_DATA_DIRS</code> path, e.g.: | ||
{{file| | {{file|3=export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/share:/var/lib/flatpak/exports/share:$HOME/.local/share/flatpak/exports/share|name=.profile|lang=}} | ||
export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/share:/var/lib/flatpak/exports/share:$HOME/.local/share/flatpak/exports/share | |||
This is also required when installing <code>flatpak</code> on a per-user basis. | This is also required when installing <code>flatpak</code> on a per-user basis. | ||
To | == Usage == | ||
=== Declarative === | |||
To manage Flatpak declaratively, you can either use [https://github.com/gmodena/nix-flatpak nix-flatpak] or [https://github.com/in-a-dil-emma/declarative-flatpak declarative-flatpak] | |||
In the event of a Nix rollback, both modules will reinstall the previously declared Flatpak packages | |||
==== [https://github.com/gmodena/nix-flatpak nix-flatpak] ==== | |||
A convergent approach to Flatpak management where refs are managed in place | |||
Flatpak packages are not cached in the Nix store | |||
It supports flakes or [[Home Manager|home-manager]], but doesn't support non-flakes only | |||
<small>For more details, see [https://github.com/gmodena/nix-flatpak/discussions/168 nix-flatpak/discussions/168]</small> | |||
==== [https://github.com/in-a-dil-emma/declarative-flatpak declarative-flatpak] ==== | |||
A congruent approach to Flatpak management where changes are designed to be atomic, ensuring that either they succeed or nothing happens. This module uses a temporary installation and then overwrites the current one. | |||
It supports non-flake, flakes, and [[Home Manager|home-manager]] | |||
< | <small>For more details, see [https://github.com/in-a-dil-emma/declarative-flatpak/issues/44 declarative-flatpak/issues/44]</small> | ||
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo | |||
=== Imperative === | |||
==== Terminal User Interface ==== | |||
To manage Flatpak imperatively, you can use [https://docs.flatpak.org/en/latest/using-flatpak.html the <code>flatpak</code> command] ([https://docs.flatpak.org/en/latest/flatpak-command-reference.html <code>flatpak</code> Command Reference Documentation]) | |||
===== Example ===== | |||
<syntaxhighlight lang="console">$ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo | |||
$ flatpak update | $ flatpak update | ||
$ flatpak search | $ flatpak search Flatseal | ||
$ flatpak install flathub | $ flatpak install flathub com.github.tchx84.Flatseal | ||
$ flatpak run org. | $ flatpak run com.github.tchx84.Flatseal</syntaxhighlight> | ||
</ | |||
==== Graphical User Interface ==== | |||
To install Flatpaks graphically, you can use [https://apps.gnome.org/en-GB/Software/ the GNOME Software Application] ([https://search.nixos.org/packages?show=gnome-software <code>gnome-software</code> in nixpkgs]) | |||
<small>'''Note''': installing Flatpaks through it is imperative</small> | |||
==== Configure Repositories Globally ==== | |||
{{Warning|This assumes you are not installing Flatpak packages [https://wiki.nixos.org/wiki/Flatpak#Declarative declaratively] (using [https://wiki.nixos.org/wiki/Flatpak#nix-flatpak nix-flatpak] or [https://wiki.nixos.org/wiki/Flatpak#declarative-flatpak declarative-flatpak]) | |||
Otherwise, the following section could conflict with them | |||
If you are, prefer using [https://wiki.nixos.org/wiki/Flatpak#nix-flatpak nix-flatpak]'s <code>services.flatpak.remotes</code> or [https://wiki.nixos.org/wiki/Flatpak#declarative-flatpak declarative-flatpak]'s <code>services.flatpak.remotes</code> instead}} | |||
To automatically configure Flatpak repositories for all users, one can add this snippet to <code>configuration.nix</code>:{{file|3=systemd.services.flatpak-repo = { | |||
wantedBy = [ "multi-user.target" ]; | |||
path = [ pkgs.flatpak ]; | |||
script = '' | |||
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo | |||
''; | |||
};|name=/etc/nixos/configuration.nix|lang=nix}} | |||
== Development == | == Development == | ||
Line 43: | Line 82: | ||
=== Build a Flatpak project === | === Build a Flatpak project === | ||
The following example builds a demo | The following example builds a demo app of the [https://github.com/GNOME/libadwaita libadwaita] repository using <code>flatpak-builder</code>, installs it locally in the user space and runs it. First install <code>flatpak</code> and <code>flatpak-builder</code> on your system | ||
{{file| | {{file|3=services.flatpak.enable = true; | ||
services.flatpak.enable = true; | environment.systemPackages = [ | ||
environment.systemPackages = [ pkgs.flatpak-builder ]; | pkgs.flatpak-builder | ||
];|name=/etc/nixos/configuration.nix|lang=nix}} | |||
Clone, build and run the example project | Clone, build and run the example project. | ||
< | <syntaxhighlight lang="console">$ flatpak remote-add --if-not-exists gnome-nightly https://nightly.gnome.org/gnome-nightly.flatpakrepo | ||
$ flatpak remote-add --if-not-exists gnome-nightly https://nightly.gnome.org/gnome-nightly.flatpakrepo | $ flatpak install gnome-nightly org.gnome.Sdk org.gnome.Platform | ||
$ flatpak install org.gnome.Sdk | $ git clone https://gitlab.gnome.org/GNOME/libadwaita.git | ||
$ git clone https://gitlab.gnome.org/GNOME/ | $ cd libadwaita | ||
$ cd | $ nix shell nixpkgs#appstream | ||
$ flatpak-builder --user --install | $ flatpak-builder --disable-tests --user --install build demo/org.gnome.Adwaita1.Demo.json | ||
$ flatpak run | $ flatpak run org.gnome.Adwaita1.Demo.json</syntaxhighlight> | ||
</ | |||
Note that the <code>gnome-nightly</code> repository and | Note that the <code>gnome-nightly</code> repository and the <code>appstream</code> dependency are especially required for this specific project and might be different for other Flatpak projects. | ||
== Tips and tricks == | == Tips and tricks == | ||
=== Emulate Flatpaks of different architecture === | === Emulate Flatpaks of different architecture === | ||
It is possible to install and run Flatpaks which were compiled for a different platform. In this example we | It is possible to install and run Flatpaks which were compiled for a different platform. | ||
flatpak install | |||
flatpak run | In this example we imperatively install the application "Metronome" <code>aarch64</code> Flatpak package and run it (regardless of the architecture of the host, but in that case, it was <code>x86_64</code>):<syntaxhighlight lang="console">$ flatpak install flathub com.adrienplazas.Metronome --arch=aarch64 | ||
</syntaxhighlight>To support emulation with Qemu, [[QEMU#Run binaries of different architecture|following Binfmt configuration]] is required. | $ flatpak run com.adrienplazas.Metronome</syntaxhighlight>To support emulation with Qemu, [[QEMU#Run binaries of different architecture|following Binfmt configuration]] is required. | ||
== Troubleshooting == | == Troubleshooting == |