Why chrome doesn't see plugins installed into /usr/local/lib/browser_plugins?

[Evan Martin]

I wrote the code in this area for Chrome, years ago.

The various unixes are hilariously fragmented in this area: even
different Linux distros demand different plugin directories[1].  My
recollection is that nspluginwrapper has an enormous list of
directories to scan, while Chrome's is more modest.

As far as I know there's no standard place to look for browser
plugins, so I tried to make Chrome match the code in Firefox.
However, it could be that Firefox had different code for FreeBSD, and
I likely ignored that code when writing the Chrome code.

Here's a link to the list of paths searched in Chrome:
  http://code.google.com/searchframe#OAMlx_jo-ck/src/webkit/plugins/npapi/plugin_list_posix.cc&l=144
(note: the word "posix" in these files is a shorthand for "unix-like
systems that aren't weird like macos", which I know isn't what posix
means)

[1] http://archives.gentoo.org/gentoo-dev/msg_a44fefe7cd70694cf9e7327134c89b5f.xml

On Fri, Nov 16, 2012 at 4:57 PM, Yuri <yuri at rawbw.com> wrote:
> On my system chrome has different set of plugins than firefox. Firefox has
> many more. It looks like chrome only picks them from ~/.mozilla/plugins,
> while firefox also looks for them in /usr/local/lib/browser_plugins.
> Some plugins only get installed into the latter directory, for ex.
> www/plugger installs /usr/local/lib/browser_plugins/plugger/npplugger.so and
> it doesn't appear in chrome at all unless one makes a symbolic link in
> ~/.mozilla/plugins.
>
> So why chrome isn't looking in /usr/local/lib/browser_plugins?
>
> Yuri
> _______________________________________________
> freebsd-chromium at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe at freebsd.org"