Summary: | sys-apps/portage-3.0.38.1: unable to unmask USE-flag masks from base profile | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Fabian Groffen <grobian> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ionen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabian Groffen
2022-10-09 10:44:06 UTC
Try doing it in /etc/portage/profile/package.use.mask? Yuck. Ok, that solves this thing. Horrible inconsistency. Yeah, I've never understood the difference either and I still wonder if there's a bug lurking or something. You're not alone! Too quick here, big thanks for pointing me in the right direction here! I just did man portage, and it is in the list as you mention, things like these: https://wiki.gentoo.org/wiki//etc/portage/package.mask suggest that my memory is probably right, and it used to work. This changed or something? Anyway, problem solved. /etc/portage is portage's own configuration files, and does not implement a package.use.mask. /etc/portage/profile is PMS-style profile files which can be anything that's valid in profiles, like an overlay on top of the profile. /etc/portage/package.mask and /etc/portage/profile/package.mask both exists but don't work the same (e.g. can't use "*/name" in the latter, profiles need the category). |