Summary: | portage should support profiles/ in overlays | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Stefan Schweizer (RETIRED) <genstef> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Schweizer (RETIRED)
![]() (In reply to comment #0) > overlays should be able to package.mask and package.unmask as well as adding > default useflags and USE_EXPAND There are 2 different types of config files that you seem to be mixing here. Look at `man portage` and note that there are different files supported in the /etc/make.profile/ section vs. the /usr/portage/profiles/ section. - package.mask: available - package.unmask: only user config setting, multiple locations are difficult due to ordering problems - default use flags / USE_EXPAND: available (just put your own profile in the overlay) |