| Summary: | emerge manpage appears to be truncated | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Neil Skrypuch <gentoo> |
| Component: | [OLD] Portage Documentation | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | rick4711 |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 147007 | ||
Thanks, it's fixed in svn r4663. The problem was some quotes that weren't properly escaped. This has been released in 2.1.2_pre2-r9. *** Bug 154873 has been marked as a duplicate of this bug. *** |
Near the bottom of the emerge manpage, we have this: KEYWORDS The KEYWORDS variable in an ebuild file is also used for masking a package still in testing. There are architecture-specific keywords for each package that let portage know which systems are compatible with the package. Packages which compile on an architecture, but have not been proven to be "stable", are masked with a tilde (~) in front of the architecture name. emerge examines the ACCEPT_KEYWORDS environment variable to allow or disallow the emerging of a package masked by KEYWORDS. To inform emerge that it should build these 'testing' versions of packages, you should update your /etc/portage/package.key- words file to list the packages you want the The sentence at the end drops off in the middle, which I suspect was not intended. This is with Portage 2.1.1.