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

Khem Raj raj.khem at gmail.com
Wed Jul 30 02:28:55 UTC 2014


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



More information about the Openembedded-devel mailing list