From owner-freebsd-chromium@FreeBSD.ORG Tue Nov 20 21:51:21 2012 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C806895B for ; Tue, 20 Nov 2012 21:51:21 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id AA4108FC08 for ; Tue, 20 Nov 2012 21:51:21 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id qAKLpJ6u014772; Tue, 20 Nov 2012 13:51:20 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <50ABFB57.5020700@rawbw.com> Date: Tue, 20 Nov 2012 13:51:19 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121118 Thunderbird/16.0.2 MIME-Version: 1.0 To: Evan Martin Subject: Re: Why chrome doesn't see plugins installed into /usr/local/lib/browser_plugins? References: <50A6E116.4010709@rawbw.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 21:51:21 -0000 On 11/20/2012 12:20, Evan Martin wrote: > 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) Interesting. /usr/ports/www/firefox/Makefile.webplugins elaborates about where plugins should be installed, and locally defines WEBPLUGINS_LIBDIR as ${PREFIX}/lib/browser_plugins. Some other ports include www/firefox/Makefile.webplugins. But looks like chrome doesn't include it. I think the best approach is to migrate the definition of plugin directory into /usr/ports/Mk and make chrome and all other browsers follow it too. Yuri