Summary: | Overlays should be able to override some profile configuration | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Fat-Zer <fatzer2> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | mva |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fat-Zer
2024-01-03 22:32:44 UTC
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/`). |