| Summary: | Document that keywords are optional in package.keywords | ||
|---|---|---|---|
| Product: | [OLD] Docs on www.gentoo.org | Reporter: | Marius Mauch <genone> |
| Component: | Installation Handbook | Assignee: | nm (RETIRED) <nightmorph> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | docs-team |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Thanks for reporting. Dunno how we missed cleaning this up -- no one should be specifying the actual arch keyword. Fixed in CVS. |
Since package.keywords support was added to portage 7 years ago the specification of keywords after the package atom has been optional: If no keyword is specified portage will default to ~arch. That is what people want to do in >90% of all cases anyway, so not specifying a keyword should actually be the normal case as it has several other advantages as well: - same format can be used for package.{mask,unmask,keywords}, which is useful for unmasking larger groups of packages - package.keywords becomes arch-neutral, so the same file can be used on different systems - less user confusion about the correct syntax for keywords This should be reflected in the documentation (in hb-portage-branches.xml), I recommend to simply drop any keyword references in the "Mixing Stable with Testing" section.