From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: 70508@debbugs.gnu.org
Cc: 宋文武 <iyzsong@member.fsf.org>
Subject: [bug#70508] [PATCH] services: Add gvfs-service-type.
Date: Mon, 22 Apr 2024 21:05:14 +0800 [thread overview]
Message-ID: <87frvd5z05.fsf@envs.net> (raw)
In-Reply-To: <d9f2d24c28021de758b35f3115d45c9ff70ffd09.1713789696.git.iyzsong@member.fsf.org> (iyzsong@envs.net's message of "Mon, 22 Apr 2024 20:42:13 +0800")
From Patch1:
> * gnu/packages/xfce.scm (thunar)[build-system]: Switch to glib-or-gtk-build-system.
>
From Patch2:
> * gnu/services/desktop.scm (gvfs-service-type): New variable.
> (gvfs-configuration, make-gvfs-configuration, gvfs-configuration?,
> gvfs-package): New procedures.
> (<gvfs-configuration>): New record.
> * doc/guix.texi (Desktop Services): Document it.
Both patches are needed technically, as GIO applications needed to be
wrapped with GIO_EXTRA_MODULES; and udisks, gvfs available as dbus
services. While it will still works with only Patch2, due to
gvfs-service-type also introduces GIO_EXTRA_MODULES via
gvfs-service-type -> udisks-service->type -> udisks -> glib dependencies
by chance, but on a foreign system or when the system side
libgvfsdbus.so is not ABI compatible with applicaiton's GLib, I guess
Patch1 could make application works as long as the GVfs dbus interface
is compatible.
next prev parent reply other threads:[~2024-04-22 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 1:47 [bug#70508] [PATCH] gnu: thunar: Use glib-or-gtk-build-system iyzsong--- via Guix-patches via
2024-04-22 2:47 ` 宋文武 via Guix-patches via
2024-04-22 12:42 ` [bug#70508] [PATCH] services: Add gvfs-service-type iyzsong--- via Guix-patches via
2024-04-22 13:05 ` 宋文武 via Guix-patches via [this message]
2024-04-29 1:02 ` bug#40885: " 宋文武 via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frvd5z05.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=70508@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=iyzsong@member.fsf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.