gecko-mediaplayer and /usr/lib/firefox/plugins -> ../mozilla/plugins symlink

Mike Hommey mh at glandium.org
Mon May 17 09:31:20 UTC 2010


On Mon, May 17, 2010 at 11:27:21AM +0200, Cesare Tirabassi wrote:
> >Brandon reported trouble unpacking the latest version of gecko-mediaplayer.
> >The package contents include
> >
> >  /usr/lib/mozilla/plugins/gecko-mediaplayer.so (a file)
> >  /usr/lib/firefox/plugins/gecko-mediaplayer.so -> ../../mozilla/plugins/gecko-mediaplayer.so (a symlink)
> >
> >Unfortunately, some setups include a symlink that makes these paths the
> >same.
> 
> If I could get rid of ALL the symlinks in the package I would indeed
> be an happier person.
> Having said that, and considering backports, the actual plugin
> situation (*) and the fact that this is a one-off problem I'm not very
> inclined to this (yet). After squeeze is released I think I should
> revisit this but I also think some effort should be done
> distribution-wise (also including derivatives, I cc the Debian and
> Ubuntu mozilla teams).
> 
> C.
> (*) There is a general trend to steer from the old harcoded path, or
> at least try to have a standard location, which seems to be at least
> followed by firefox (iceape), konqueror and chromium-browser. So far,
> all plugin packages I know of still use symlinks though, I believe for
> back-compatibility.

/usr/lib/mozilla/plugins is used by all mozilla-based products,
including upstream, and as such is the canonical location in debian.
AFAIK, webkit will look there (that's upstream iirc), so I guess
chromium would, too.

Mike



More information about the pkg-mozilla-maintainers mailing list