On 2016-04-22 19:23, Trevor Woerner wrote:
On Mon 2016-04-18 @ 11:37:19 AM, S. Lockwood-Childs wrote:
If you just plan on using chromium as a normal browser without such
bells and whistles, don't worry about the keys and get rid of the
warning by setting them as blank when you start up chromium

export GOOGLE_API_KEY=" "
export GOOGLE_DEFAULT_CLIENT_ID=" "
export GOOGLE_DEFAULT_CLIENT_SECRET=" "

Yes, that works. Or you could use the 'disable-api-keys-info-bar'
packageconfig option too.


Thanks, that's good to know.

Any ideas on what to do about the SSL error (all https:// pages fail)?

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to