From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: How to handle required plugins and dbus services for GNOME Programs?
Date: Fri, 10 Jul 2015 23:24:18 +0200 [thread overview]
Message-ID: <87mvz37lkt.fsf@gnu.org> (raw)
In-Reply-To: <87egkhrgfd.fsf@netris.org> (Mark H. Weaver's message of "Thu, 09 Jul 2015 02:30:46 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> So, at this point my inclination is to do the following:
>
> * Add 'dconf' to the propagated-inputs of 'totem', since totem needs
> dconf services to be available on the user session D-Bus.
>
> * Add a wrapper for 'totem' that add prefixes to both
> GST_PLUGIN_SYSTEM_PATH and GRL_PLUGIN_PATH to ensure reliable access
> to a baseline set of plugins needed for proper functioning of 'totem'.
> This includes grilo-plugins, gst-plugins-base, and gst-plugins-good.
> IMO, this hard-coded set of plugins should exclude patent-encumbered
> codecs, so no gst-libav or gst-plugins-ugly.
>
> Please see the attached 'totem' package. To simplify things, the values
> of the GST_PLUGIN_SYSTEM_PATH and GRL_PLUGIN_PATH environment variables
> are taken directly from the build environment (using 'getenv') and
> propagated unchanged into the created wrapper.
>
> What do you think?
Sounds good. Thanks for moving forward!
Ludo’.
next prev parent reply other threads:[~2015-07-10 21:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-06-24 6:06 ` [PATCHES] Add totem Mark H Weaver
2015-06-24 20:21 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
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
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
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=87mvz37lkt.fsf@gnu.org \
--to=ludo@gnu.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 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).