Which Portage settings actually prevent a locally built binpkg from being installed on a production host with mismatched USE flags?
I maintain a Gentoo build host that produces binary packages for a small fleet of production servers. The goal is reproducible deployment: a package emerged locally should either install cleanly in production or be rejected with a clear mismatch, never silently installed with different dependency assumptions. The uncertainty is around how much Portage actual
gentoo