[Pkg-chromium-maint] Bug#748867: Fix/workaround for Google API key problem.

[Carlos Alberto Lopez Perez]

Another option is setting the Google API Keys in the environment [1].

So, it should be enough to create a file at /etc/chromium.d that
exports the keys. (/usr/bin/chromium sources all files on that dir)

This works for me:

$ cat /etc/chromium.d/googleapikeys 
export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"


(BTW: This keys are the Debian Google API keys that used to be included 
in older Chromium packaging debian/rules)

[1] http://www.chromium.org/developers/how-tos/api-keys

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 883 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20141013/10e1e870/attachment.sig>