Gentoo Profile Defaults and Binary Package USE Flag Interoperability

Integration of System Profiles and Prebuilt Binaries

Gentoo utilizes system profiles to define default USE flags, which dictate compile-time features for ebuilds. When deploying binary packages (prebuilts) across different environments, the target system's local USE flag configuration in /etc/portage/make.conf may diverge from the flags used during the binary's original build process.

This creates a potential mismatch where a binary package is installed on a system with conflicting profile defaults or local overrides. Because USE flags can alter the resulting binary's symbols and dependencies, there is uncertainty regarding how Portage handles the validation of these flags during the installation of a prebuilt package versus a source-based build.

What is the mechanism for detecting USE flag mismatches between a binary package and the local system profile? Does the package manager enforce flag compatibility at the time of installation, or is this verified only at runtime through missing symbols?