To reproduce our issue on our Acer CXI3:
(1) entered developer mode on the Chrome device
(2) ran dev-install
(3) fixed symlinks to /usr/bin/Python27 (as described under this ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=942276)
(4) ran emerge -s sys-process/
What is the expected result?
When running search command through Emerge, we expect to be able to install any package we see on the gentoo linux package directory: https://packages.gentoo.org/categories
What happens instead?
Our search queries only return a very small subset of available gentoo packages.
We're unsure at this point in time if our limited package availability is related to an issue with the Chrome OS or with our emerge install. We followed the directions at this link: https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/install-software-on-base-images , and we have no luck seeing the package we need for our machine. We know it's not an issue related to an enterprise enrolled device, so our machine isn't locked down by any policy that would limit package availability.
Here is our emerge --info output:
!!! No gcc found. You probably need to 'source /etc/profile'
!!! to update the environment of this terminal and possibly
!!! other terminals also.
Portage 2.3.49 (python 2.7.10-final-0, unavailable, [unavailable], unavailable, 4.4.176-16085-g5e7e7a424abd x86_64)
System uname: Linux-4.4.176-16085-g5e7e7a424abd-x86_64-Intel-R-_Celeron-R-_CPU_3865U_@_1.80GHz-with-glibc2.2.5
KiB Mem: 3937392 total, 2104904 free
KiB Swap: 5767664 total, 5767664 free
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gentoo-release /etc/terminfo"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
Unset: CHOST, ENV_UNSET, PORTAGE_BUNZIP2_COMMAND
You should talk to the Chrome OS people about this, not the people who run the meta-distribution that Chrome OS is (or once was?) based on.