unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Suggest installing gvfs.
Date: Tue, 29 Nov 2016 23:34:26 +0100	[thread overview]
Message-ID: <87a8ch29vx.fsf@elephly.net> (raw)
In-Reply-To: <8760n6ndh3.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> “gvfs” is useful for more than just GNOME.  For a long time I tried to
>> figure out why USB devices would not be mounted automatically in Xfce
>> and I ran gvfsd and the gvfs-* device monitor daemons manually — until
>> today when I understood that these daemons are supposed to be started
>> automatically if only the DBUS service files were found.
>>
>> We probably should add it to the “gnome” meta-package, and additionally
>> document in the manual that gvfs must be installed system-wide to allow
>> DBUS to find the service files and start the monitoring daemons on
>> demand.
>
> If it’s not specific to GNOME, what about adding it to
> ‘%desktop-services’?

How would that work?  “gvfs” doesn’t provide any services that would be
run as root.  It only comes with dbus service files; the daemons are
started as the current user on demand over dbus when certain libraries
are loaded.

Should I write dbus services for each of the daemons and extend the
dbus-root-service-type?  (I’m not sure how to do this but I could try.)

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
http://elephly.net

  reply	other threads:[~2016-11-29 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 18:47 [PATCH] doc: Suggest installing gvfs Ricardo Wurmus
2016-11-28 19:16 ` Mathieu Lirzin
2016-11-28 21:26   ` Ricardo Wurmus
2016-11-28 21:11 ` Ludovic Courtès
2016-11-28 22:22   ` Ricardo Wurmus
2016-11-29 22:11     ` Ludovic Courtès
2016-11-29 22:34       ` Ricardo Wurmus [this message]
2016-11-30 13:15         ` Ludovic Courtès
2016-12-19 13:55           ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8ch29vx.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).