[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to handle required plugins and dbus services for GNOME Programs?
From: |
Ludovic Courtès |
Subject: |
Re: How to handle required plugins and dbus services for GNOME Programs? |
Date: |
Fri, 10 Jul 2015 23:24:18 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Mark H Weaver <address@hidden> 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’.