<div><span class="gmail_quote">On 5/31/07, <b class="gmail_sendername">Josselin Mouette</b> <<a href="mailto:joss@debian.org">joss@debian.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Le mercredi 30 mai 2007 à 13:01 +0300, Ilya Konstantinov a écrit :<br>> Package: libgnomevfs2-extra<br>
> Version: 2.18.1-2<br>><br>> When this package is installed, libgnomevfs gains extra abilities.<br>> However, currently gstreamer0.10-gnomevfs has no way of knowing this<br>> (see GStreamer bug 350477 [1]) and therefore if GStreamer has already
<br>> registered the GnomeVFS plugin, it won't be re-registered with the<br>> newly-supported protocols.<br>><br>> A temporary workaround could be to<br>> touch /usr/lib/gstreamer-0.10/libgstgnomevfs.so, if it exists, on
<br>> installation, so GStreamer would re-register it.<br><br>Sorry, but that looks like the ugliest possible solution to this issue.<br><br>@GStreamer maintainers: is there a clean way to re-rerun the<br>registration process in a postinst script
</blockquote>
<div> </div>
<div>No, since registration is per-user. Each user has a cached registry in his home directory.</div>
<div> </div>
<div>My solution was proposed in the GStreamer bug report and it's entirely safe (can you think of anything bad this can result in?). Until GStreamer has an infrastructure to handle those things, we don't have much of a choice.
</div></div>