all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: How to handle required plugins and dbus services for GNOME Programs?
Date: Tue, 30 Jun 2015 20:05:30 +0200	[thread overview]
Message-ID: <CAKrPhPPgaD0RXys=+z2q+iZfdpa6nRQHzM=U9MtH9tJxWjbjkA@mail.gmail.com> (raw)
In-Reply-To: <87pp4dgp7c.fsf@netris.org>

On Tue, Jun 30, 2015 at 6:01 PM, Mark H Weaver <mhw@netris.org> wrote:
> Federico Beffa <beffa@ieee.org> writes:
>
>> On Mon, Jun 29, 2015 at 1:35 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> 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?
>>
>> IMO, given that every GLib based program needs it, the right thing to
>> do is to make it an implicit input of 'glib-or-gtk-build-system'.
>
> Many GLib based programs do *not* need dconf.  So far, I know of only
> two programs in Guix that need dconf.  It is a GNOME thing, not a GLib
> thing.

You are right. I got confused. 'dconf' is a backend of 'GSettings'.

>
> Also, I wouldn't be surprised if one of the transitive inputs of dconf
> uses 'glib-or-gtk-build-system', which would lead to a circularity
> problem.
>
>> In a similar way, every GLib based program/library makes use of sound
>> themes.
>
> That's not true either.
>
> It may be that we should have a 'gnome-build-system' that's based on
> 'glib-or-gtk-build-system' but adds these extra implicit inputs and
> arranges for more environment variables to be set in the wrappers.

The distinction between "a GNOME application" and an application
making use of "a subset of the GNOME infrastructure and requiring
'dconf' and/or 'libcanberra'" doesn't appear to be clear cut to me:

* GLib is hosted on the GNOME site. Isn't it part of the GNOME project?
* I get the warnings:

    Gtk-Message: Failed to load module "canberra-gtk-module"
    GLib-GIO-Message: Using the 'memory' GSettings backend.  Your
settings will not be saved or shared with other     applications.

  even when starting 'emacs' and the first one even when importing
'matplotlib' inside of a python shell. As far as I know, these two
programs are not part of GNOME.

Adding 'dconf' and 'libcanberra' as default inputs to
'glib-or-gtk-build-system' would make many of these problems go away,
with the only drawback of a possibly unused entry in an environment
variable. However, if you want to be super accurate then yes, this
will not do.

Fede

  reply	other threads:[~2015-06-30 18:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  7:28 How to handle required plugins and dbus services for GNOME Programs? Federico Beffa
2015-06-25 11:49 ` Ludovic Courtès
2015-06-25 12:16   ` Federico Beffa
2015-06-29 11:35     ` Ludovic Courtès
2015-06-30  6:52       ` Federico Beffa
2015-06-30 16:01         ` Mark H Weaver
2015-06-30 18:05           ` Federico Beffa [this message]
2015-06-30 19:28             ` Ludovic Courtès
2015-07-01 18:11               ` Federico Beffa
2015-07-23 18:16         ` Cook, Malcolm
2015-07-23 19:33           ` Federico Beffa
2015-07-24 18:41             ` Cook, Malcolm
2015-07-27 20:13               ` Federico Beffa
2015-06-25 14:34   ` Mark H Weaver
  -- strict thread matches above, loose matches on Subject: below --
2015-06-21  4:21 [PATCHES] Add totem Mark H Weaver
2015-06-22 19:24 ` Ludovic Courtès
2015-06-24  5:58   ` How to handle required plugins and dbus services for GNOME Programs? Mark H Weaver
2015-06-24 15:45     ` 宋文武
2015-06-25  4:07       ` Mark H Weaver
2015-06-25  7:42         ` 宋文武
2015-06-24 20:47     ` Ludovic Courtès
2015-06-25  5:00     ` David Hashe
2015-07-09  6:30     ` Mark H Weaver
2015-07-09 13:00       ` 宋文武
2015-07-10 21:24       ` 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

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

  git send-email \
    --in-reply-to='CAKrPhPPgaD0RXys=+z2q+iZfdpa6nRQHzM=U9MtH9tJxWjbjkA@mail.gmail.com' \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.