Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#41577 - [chromium] provide google API keys at runtime rather than build time
Attached to Project:
Arch Linux
Opened by Florez Brownlee (frownlee) - Saturday, 16 August 2014, 17:04 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 26 August 2014, 22:38 GMT
Opened by Florez Brownlee (frownlee) - Saturday, 16 August 2014, 17:04 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 26 August 2014, 22:38 GMT
|
DetailsDescription:
As per http://www.chromium.org/developers/how-tos/api-keys, google API keys can be provided at runtime rather than at build time. Additional info: * package version(s): all * config and/or log files etc. Steps to reproduce: Install chromium, sign in to google account. Check https://security.google.com/settings/security/permissions?pli=1 which shows the Arch build of chromium having full access. Using the google provided chrome shows Google Chrome instead. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Tuesday, 26 August 2014, 22:38 GMT
Reason for closing: Won't implement
Tuesday, 26 August 2014, 22:38 GMT
Reason for closing: Won't implement
Comment by Evangelos Foutras (foutrelis) -
Sunday, 17 August 2014, 04:29 GMT
I don't understand what the problem is.