[oe] [meta-browser][PATCH 1/2] chromium: Add PACKAGECONFIG for disabling API keys info bar

[Otavio Salvador]

On Tue, Jul 29, 2014 at 5:35 PM, Khem Raj <raj.khem at gmail.com> wrote:
> On Tue, Jul 29, 2014 at 3:22 AM, Carlos Rafael Giani
> <dv at pseudoterminal.org> wrote:
>> +Upstream-Status: Inappropriate [other]
>> +The info bar is not a bug; it is just undesirable in some use cases.
>> +A clean approach - which requires discussion with upstream - is to
>> +disable it by using a command line option.
>> +
>> +Signed-off-by: Carlos Rafael Giani <dv at pseudoterminal.org>
>
> I think it would be better to get a suggested solution which is
> acceptable upstream.

There are customers who don't need to use the Google APIs so they are
not willing to make an API key and instead they prefer to drop the
warning and keep using the Chromium as an application platform. We've
been involved in a couple of projects lately where this happened.

Chromium's upstream advice is to generate an API and use it to deploy;
I think in the meta-browser's case this is sub-optimal as we'll end
having several products and customers using our key and not making
their own ones.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750