[arch-multilib] Browser plugin location
Hi, Yesterday I installed the flashplugin from this repo. but this caused the flash plugin in Opera (64 bit) to stop working because Opera doesn't use nspluginwrapper (and blacklists it because it causes problems) because it can run 32 bits plugins natively. Because the flash plugin isn't in its plugin path (/usr/lib/mozilla/plugins and /usr/lib/opera/plugins) it doesn't find the plugin. I've test if Opera finds the plugin when placed in /usr/lib32/mozilla/plugins and this seems to be the case. So its probably best to place the 32 bits plugins in /usr/lib32/mozilla/plugins instead of the /usr/lib/nspluginwrapper/i386/plugins so browsers who can run the 32 bit plugin still find it (because it isn't in an "obscure" folder) and other browsers still use the nspluginwrapper plugin in /usr/lib/mozilla/plugins/. This solution also keeps the /usr/lib folder free of 32 bit libraries. I've created a patch for the PKGBUILD and .install script so the flash plugin gets installed in the /usr/lib32/mozilla/plugins path. diff -U 2 /var/abs/multilib/flashplugin//flashplugin.install ./flashplugin.install --- /var/abs/multilib/flashplugin//flashplugin.install 2010-08-27 06:11:59.000000000 +0200 +++ ./flashplugin.install 2010-08-27 16:17:21.413333339 +0200 @@ -1,4 +1,4 @@ post_upgrade() { - /usr/bin/nspluginwrapper -i /usr/lib/nspluginwrapper/i386/plugins/libflashplayer.so + /usr/bin/nspluginwrapper -i /usr/lib32/mozilla/plugins/libflashplayer.so } diff -U 2 /var/abs/multilib/flashplugin//PKGBUILD ./PKGBUILD --- /var/abs/multilib/flashplugin//PKGBUILD 2010-08-27 06:11:59.000000000 +0200 +++ ./PKGBUILD 2010-08-27 16:18:13.566666673 +0200 @@ -18,6 +18,6 @@ package() { - install -d -m755 "${pkgdir}"/usr/lib/nspluginwrapper/i386/plugins/ - install -m755 "${srcdir}"/libflashplayer.so "${pkgdir}"/usr/lib/nspluginwrapper/i386/plugins/ + mkdir -p "${pkgdir}"/usr/lib32/mozilla/plugins + install -m755 "${srcdir}"/libflashplayer.so "${pkgdir}"/usr/lib32/mozilla/plugins install -d -m755 "${pkgdir}"/usr/share/licenses/${pkgname}/ install -m644 "${_licensefile}" "${pkgdir}"/usr/share/licenses/${pkgname}/LICENSE.pdf Regards, Robert Meijers
Am 29.08.2010 12:44, schrieb Robert Meijers:
Hi,
Yesterday I installed the flashplugin from this repo. but this caused the flash plugin in Opera (64 bit) to stop working because Opera doesn't use nspluginwrapper (and blacklists it because it causes problems) because it can run 32 bits plugins natively.
The question is if you want to use our flashplugin package then. It depends on nspluginwrapper and thus pulls in many dependencies. The reason I didn't put this into the plugin path is because firefox throws a warning each time you start it, which might unnecessarily concern users. I am wondering if it wouldn't be better if you (Opera user) just added a symlink in the plugin folder or added the folder with the flash plugin to the plugin search path. I like it the way it is now, but if you feel strong about changing it, that wouldn't kill anyone either.
Thomas Bächler <thomas@archlinux.org> wrote:
The reason I didn't put this into the plugin path is because firefox throws a warning each time you start it, which might unnecessarily concern users. I am wondering if it wouldn't be better if you (Opera user) just added a symlink in the plugin folder or added the folder with the flash plugin to the plugin search path.
Robert's argument seems sensible: by the way, there is no reason why firefox (the 64-bit one) would look into a /usr/lib32 folder. -- Rémy.
2010/8/31 Thomas Bächler <thomas@archlinux.org>:
The question is if you want to use our flashplugin package then. It depends on nspluginwrapper and thus pulls in many dependencies.
The reason I didn't put this into the plugin path is because firefox throws a warning each time you start it, which might unnecessarily concern users. Just tested, Firefox doesn't look for plugins in the /usr/lib32 plugin folder (or at least doesn't throw a warning, which it does when I copy it to the /usr/lib/ one). So it is safe to place the plugin itself in
I don't mind the nsplugwrapper dependency (because I still sometimes (have to) use Firefox, so I also need the nspluginwrapper one). And I think other Opera users also need this one (with nspluginwrapper) because they probably also use/test other browsers, which probably can't run 32 bit plugins as Opera can. the /usr/lib32 folder and (at least) Firefox won't complain about a 32 bit plugin.
participants (3)
-
Robert Meijers
-
Rémy Oudompheng
-
Thomas Bächler