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

[Otavio Salvador]

On Tue, Jul 29, 2014 at 11:28 PM, Khem Raj <raj.khem at gmail.com> wrote:
> On Tue, Jul 29, 2014 at 2:51 PM, Otavio Salvador
> <otavio at ossystems.com.br> wrote:
>> 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.
>
> OK then disabling the API key is in essence suppressing the problem. I
> am fine if thats the general usecase but I doubt that

As I explained, this is the requirement for some projects we've been
involved with. The idea here is to share it in a 'reusable' way and
avoid this patch to be kept private for no good reason.

I think it is fine as is.

-- 
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