summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDanny Milosavljevic <dannym@friendly-machines.com>2025-06-09 04:44:02 +0200
committerDanny Milosavljevic <dannym@friendly-machines.com>2025-06-09 05:02:50 +0200
commit2d418933a46a92a545ccebe629470af0fc019c4b (patch)
tree474db8fbfbe72ce3a287305e0a27ec2f11142727
parent47dba6b269858e8628d63a5fd5df07c91fb91b5a (diff)
gnu: flatpak: Simplify and document.
* gnu/packages/package-management.scm (flatpak)[native-search-paths]: Add comment. <file-pattern>: Remove. Change-Id: I610939d4bd96e5c952695d76265d568e7b69433b
-rw-r--r--gnu/packages/package-management.scm14
1 files changed, 11 insertions, 3 deletions
diff --git a/gnu/packages/package-management.scm b/gnu/packages/package-management.scm
index 25224b8eb6e..39abd18bd7a 100644
--- a/gnu/packages/package-management.scm
+++ b/gnu/packages/package-management.scm
@@ -2214,11 +2214,19 @@ cp -r /tmp/locale/*/en_US.*")))
libseccomp
libxau))
(native-search-paths
- (list (search-path-specification
+ (list ;; Flatpak creates desktop files on its own.
+ ;; If those desktop files contain DBusActivatable=true, the application
+ ;; will be invoked by using dbus activation. But dbus activation
+ ;; doesn't use $PATH but rather does execve while the working directory
+ ;; is "/". That means, if the Exec entry contains just "flatpak",
+ ;; that won't be ever found.
+ ;; When flatpak creates desktop files, it uses a path from
+ ;; $FLATPAK_BINARY if set.
+ ;; See <https://codeberg.org/guix/guix/issues/438>.
+ (search-path-specification
(variable "FLATPAK_BINARY")
(separator #f)
- (files '("bin"))
- (file-pattern "^flatpak$")
+ (files '("bin/flatpak"))
(file-type 'regular))))
(home-page "https://flatpak.org")
(synopsis "System for building, distributing, and running sandboxed desktop