all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/4] gnu: libcanberra: Add propagated-input.
Date: Sun, 21 Dec 2014 12:06:30 +0100	[thread overview]
Message-ID: <87oaqxqn2h.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPM_DjRh_enBH8bNgEB7FVAkvB9C8Exyme+XwxDdGnYYSw@mail.gmail.com> (Federico Beffa's message of "Thu, 18 Dec 2014 22:14:37 +0100")

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?

Thanks,
Ludo’.

  reply	other threads:[~2014-12-21 11:06 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 [this message]
2014-12-21 15:33   ` Federico Beffa
2015-01-07 17:20     ` Federico Beffa
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=87oaqxqn2h.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.org \
    --cc=guix-devel@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.