Hi.. Saw that mplayerplug-in installs into /opt/netscape/plugins. Shouldn't it be installed into /usr/lib/nsbrowsers/plugins instead, since /opt/ is for binary-only stuff, like libflasplayer.so, wich is symlinked to /usr/lib32/nsbrowsers/plugins The totem-plugin for-example, installs its plugins in the /usr/lib/nsbrowser By installing self-built stuff in /opt/ prevents people to install a binary version of mplayerplug-in to be used in firefox-bin. In the future this is.
No, it shouldn't since it simply won't work there, it would have to be symlinked to /opt/netscape/plugins anyway, so you won't solve anything. # ls -l /usr/lib/nsbrowser/plugins/ total 40 lrwxrwxrwx 1 root root 37 2006-08-30 16:16 flashplayer.xpt -> /opt/netscape/plugins/flashplayer.xpt lrwxrwxrwx 1 root root 29 2006-07-05 15:20 gxineplugin.so -> /usr/lib/gxine/gxineplugin.so lrwxrwxrwx 1 root root 63 2006-08-12 01:46 javaplugin.so -> /usr/share/java-config-2/nsplugin/sun-jre-bin-1.5-javaplugin.so lrwxrwxrwx 1 root root 39 2006-08-30 16:16 libflashplayer.so -> /opt/netscape/plugins/libflashplayer.so lrwxrwxrwx 1 root root 32 2006-03-24 09:47 nphelix.so -> /opt/netscape/plugins/nphelix.so lrwxrwxrwx 1 root root 30 2006-07-27 03:54 nppdf.so -> /opt/netscape/plugins/nppdf.so
(In reply to comment #1) > No, it shouldn't since it simply won't work there, it would have to be > symlinked to /opt/netscape/plugins anyway, so you won't solve anything. Well it does works there, the totem-plugins are only installed in /usr/lib/nsbrowser/plugins and if you move the plugins from /opt/netscape/plugins/ to /usr/lib/nsbrowser/plugins they still work, this is because of the /usr/bin/firefox wrapper export MOZ_PLUGIN_PATH=${MOZ_PLUGIN_PATH:-/usr/lib64/nsbrowser/plugins} Why should mplayerplug-in install in /opt and not totem? They are both built from source so the are 64-bit comp. on AMD64.
Forgot to reopen bug.
Shrug... Could care less.
I have posted an updated ebuild in bug #107922 that fixes this issue.
Looking at all of the other plugins, most of them also install into /opt/netscape/plugins, probably for compatibility reasons (maybe not all mozilla compatible browsers have that wrapper?) If a -bin version of mplayerplug-in were to exist, it would definitely block mplayerplug-in since we don't want two versions of the same plugin to be able to load at the same time. I'll comment on your ebuild patch in the other bug. I'll leave this open for now and check other browsers to see if there are any issues with moving the installed directory.
I decided to move it, thanks for the suggestion. The change is incorporated in 3.40.
