-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Problem
GRPM solver currently doesn't filter packages by KEYWORDS. This means unkeyworded packages (like live/9999 ebuilds) are selected even though Portage would filter them out.
Example: sys-devel/gcc-16.0.9999 has no KEYWORDS, so Portage won't select it by default. But GRPM does.
Root Cause
The pkg.Package struct doesn't have a Keywords field, and there's no keyword filtering in the solver.
Expected Behavior
Solver should:
- Parse KEYWORDS from ebuild
- Filter packages that don't have KEYWORDS matching
ACCEPT_KEYWORDSfrom make.conf - By default, accept only stable keywords (e.g.,
amd64) - With
~amd64in ACCEPT_KEYWORDS, also accept testing packages
Implementation Plan
- Add
Keywords []stringfield topkg.Package - Parse KEYWORDS in ebuild parser
- Add
KeywordManagersimilar toMaskManager - Integrate keyword filtering in solver
Related
- v0.8.1 implements package.mask filtering (Solver ignores package.mask - selects masked packages (e.g., gcc-16) #46)
- This issue tracks the missing keyword filtering
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request