Subject: Re: bug#41025: blueman does not start

From: Marius Bakke <[email-masked]>
Date: Sun, 10 May 2020 23:29:05 +0200

Raghav Gururajan <[email-masked]> writes:

> +         ;; Prevent the autogen.sh script to carry out the configure
> +         ;; script, which has not yet been patched to replace /bin/sh.
> +         (add-before 'bootstrap 'setenv
> +           (lambda _
> +             (setenv "NOCONFIGURE" "TRUE")
> +             #t))

This phase is no longer necessary after the recent 'core-updates' merge.

> +         ;; PATH is hard-coded for FHS directories.
> +         ;; Patch it to PATH used by Guix.
> +         (add-after 'patch-python-references 'patch-os-path
> +           (lambda _
> +             (substitute*
> +                 '("apps/blueman-mechanism.in" "blueman/Functions.py")
> +               (("/usr/bin:/bin:/usr/sbin:/sbin")
> +                (string-append
> +                 "~/.guix-profile/bin:"
> +                 "/run/current-system/profile/bin:"
> +                 "~/.guix-profile/sbin:"
> +                 "/run/current-system/profile/sbin"))
> +               ((":/sbin:/usr/sbin")
> +                (string-append
> +                 ":/run/current-system/profile/sbin:"
> +                 "~/.guix-profile/sbin")))
> +             #t))

These paths are "impure": the contents will differ from system to
system, and are also unavailable in e.g. 'guix environment -container'.
It might be better to patch these directories to something nonsensical
like "/no-such-path": that ensures we catch any missing references.

That's not always feasible though, but hopefully works for this
package.