Bug#426694: GStreamer GnomeVFS plugin fails to recognize extra protocols

David Schleef ds at schleef.org
Thu May 31 18:31:14 UTC 2007

On Thu, May 31, 2007 at 10:44:16AM +0200, Loïc Minier wrote:
> On Thu, May 31, 2007, Josselin Mouette wrote:
> > This looks like a design flaw. The only way to make it work correctly is
> > to make gstreamer0.10-gnomevfs depend on libgnomevfs2-extra. We should
> > also try to make this registry system-wide in the future, so that we can
> > trigger a rebuild.
>  No, it was system-wide in the past already; this was removed in favor
>  of per-user registry.  I don't know the rationale for the change, but I
>  imagine it's due to being able to install plugins in ~/ and to set the

One solution that would be less of a kludge than touching the .so is:

 - Core checks a well known file (/var/cache/gstreamer-0.10/plugin-timestamp)
   at the same time as all the .so file timestamps.  If this timestamp
   is not the same as what is contained in the registry, the core
   forces a regeneration of the entire registry.

 - When a package is installed that might affect the contents of the
   registry, but doesn't affect a relevant .so file, the post-install
   script should touch the plugin-timestamp file.

It's less of a gross hack than touching .so files, but still not a
complete solution.  IMO, a complete solution involves every project
using a decent registry system.  (yeah, right!)


More information about the Pkg-gstreamer-maintainers mailing list