Re: How to handle required plugins and dbus services for GNOME Programs?

[Ludovic Courtès]

Federico Beffa <address@hidden> skribis:

> On Thu, Jun 25, 2015 at 1:49 PM, Ludovic Courtès <address@hidden> wrote:
>> Federico Beffa <address@hidden> skribis:
>>
>>> address@hidden (Ludovic Courtès) writes:
>>
>> [...]
>>
>>>> Really?  In Evince, I can change the state of various things (such as
>>>> whether or not to view documents continuously), but those changes are
>>>> lost across restarts.  However, changes made via dconf-editor are not
>>>> lost.  Weird no?
>>>
>>> 'dconf' is responsible for handling the program configuration. For
>>> writes, it contacts D-Bus, for read it doesn't need D-Bus.
>>>
>>> https://developer.gnome.org/dconf/0.22/dconf-overview.html
>>>
>>> If 'dconf' is not available, the program reverts to a 'memory' back-end
>>> and configuration is lost upon exit.
>>
>> In this last sentence, are you referring to dconf-the-program,
>> dconf-the-library, or dconf-the-service?
>>
>> dconf-the-package is in my profile, so I would expect Evince to
>> automatically dbus-launch it when it needs to save its settings, but
>> apparently that doesn’t happen.
>
> I'm not sure about the terminology, but if you do
>
> GIO_EXTRA_MODULES=/gnu/store/...-dconf-0.22.0/lib/gio/modules evince
>
> it should work. (See comments in the 'glib-or-gtk-build-system'.)

Oh, I see.

Then, should we make dconf an implicit input of
glib-or-gtk-build-system?

Or should we add it as an explicit dependency on a case-by-case basis?

Thanks,
Ludo’.