all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/4] gnu: libcanberra: Add propagated-input.
Date: Wed, 7 Jan 2015 18:20:41 +0100	[thread overview]
Message-ID: <CAKrPhPPshkxiA6XQMQwJ-5wJBwtfe-SqcmN0LmACT6Lujv+WiQ@mail.gmail.com> (raw)
In-Reply-To: <CAKrPhPNHtP_xUJUGFvVuBrug5OKB5Td54q-5Jn1LffRPH2vf8Q@mail.gmail.com>

On Sun, Dec 21, 2014 at 4:33 PM, Federico Beffa <beffa@ieee.org> wrote:
> On Sun, Dec 21, 2014 at 12:06 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Federico Beffa <beffa@ieee.org> skribis:
>>
>>> I propose to make sound-theme-freedesktop a propagated input of
>>> libcanberra. This is because, according to the XDG sound theme
>>> specification, those event sounds should always be present and used as
>>> fall-back in case other sounds are not present.
>>>
>>> http://www.freedesktop.org/wiki/Specifications/sound-theme-spec/
>>
>> That’s not the right fix, I think.  For instance, if Evince is installed
>> in a profile, but libcanberra itself is not in the profile, then the
>> sound theme is not pulled and ends up not being used.
>>
>> Would it be possible, instead, to patch libcanberra to refer to the
>> sound-theme directory as its fallback?
>
> The location of the sound theme is specified, among other things, by
> the variable XDG_DATA_DIRS. So, if an application makes use of the
> glib-or-gtk-build-system and has the sounds as inputs, then it should
> find them.  I don't think we need to patch libcanberra in any way.
>
> With my suggestion I was trying to avoid having to specify
> sound-theme-freedesktop in addition to libcanberra in every gtk
> application (as, e.g., evince).
>
> If we make libcanberra a propagated-input of applications like evince,
> then they would automatically know the location of the sounds (by the
> inheritance of propagated inputs).

Not sure we concluded on this. Is my intention clear? Does my previous
answer address your point?

Regards,
Fede

  reply	other threads:[~2015-01-07 17:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 21:14 [PATCH 3/4] gnu: libcanberra: Add propagated-input Federico Beffa
2014-12-21 11:06 ` Ludovic Courtès
2014-12-21 15:33   ` Federico Beffa
2015-01-07 17:20     ` Federico Beffa [this message]
2015-01-07 20:11     ` Ludovic Courtès
2015-01-08 17:08       ` Federico Beffa
2015-01-08 20:39         ` Ludovic Courtès
2015-01-10 11:15           ` Federico Beffa
2015-01-10 21:13             ` Ludovic Courtès
2015-01-11  8:34               ` Federico Beffa
2015-01-11 10:59                 ` Ludovic Courtès
2015-01-11 13:04                   ` Federico Beffa
2015-01-11 13:34                     ` Federico Beffa
2015-01-12  9:22                       ` 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=CAKrPhPPshkxiA6XQMQwJ-5wJBwtfe-SqcmN0LmACT6Lujv+WiQ@mail.gmail.com \
    --to=beffa@ieee.org \
    --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 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.