Overlays should be able to override at least some profile configuration like USE/package masking for a specific arch. ------ Imaging that you have a `foo/bar` package with a `USE="baz"`. `USE="baz"` provides great optimizations but it works only on `arm` and there is no sense in porting it to other arches. In main portage tree there is an easy solution for that: <tree>/profiles/package.use.mask foo/bar baz <tree>/profiles/arch/arm/package.use.mask foo/bar -baz But if `foo/bar` is located in overlay there is no way to mask/unmask the USE flag for a specific arch, `<overlay>/profiles/arch/*` doesn't work at all. Reproducible: Always
From the portage man page, these configuration files are repo-level rather than profile-level, despite the fact that they live in a "profiles" directory: /var/db/repos/gentoo/profiles/ arch.list categories info_pkgs info_vars license_groups make.defaults package.mask package.unmask package.use package.use.force package.use.mask package.use.stable.force package.use.stable.mask profiles.desc repo_name thirdpartymirrors use.desc use.force use.local.desc use.mask use.stable.mask use.stable.force
(In reply to Zac Medico from comment #1) > From the portage man page, these configuration files are repo-level rather > than profile-level, despite the fact that they live in a "profiles" > directory: Still, overriding gentoo-repo's masks (both flags, and packages) on overlay level is impossible at all, IIRC (or, at least, huge PITA, if I remember a bit wrong)
(In reply to Zac Medico from comment #1) > From the portage man page, these configuration files are repo-level rather > than profile-level, despite the fact that they live in a "profiles" > directory: Files in `<tree>/profiles/` are repo-level, but arch-specific files in `<tree>/profiles/arch/*` are part of the profile (inherited via `parent` from e.g. `<tree>/profiles/default/linux/arm/`).
