Plz advice about emerge-${BOARD} chromeos-chrome's internal process.

[Bin]

emerge-reven chromeos-chrome doesn't embed ~/.googleapikeys.
Because...

In the ebuild file, there is add_api_keys() function.
But the function is never called by src_prepare(), since the google_apis/internal dir appears with src_unpack().

When I manually execute add_api_keys() function by src_prepare() modification, It works.

emerge-reven chromeos-chrome embeds ~/.googleapikeys.

Now I am curious what makes the google_apis/internal dir? and what is the purpose?
I didn't add any IUSE flags (chrome_internal flag is offed), but why it appears and screw up?

[Raul Rangel]

google_apis/internal is creates by the chrome source checkout: https://chromium.googlesource.com/chromium/src/+/main/DEPS#4804

You need to have an internal check out for that git repo to be present.

[Dominik Behr]

You may want to read this article https://www.chromium.org/developers/how-tos/api-keys/