| Summary: | new PORTAGE_BINHOST protocol | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
| Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | solar, ulm, wolf31o2, wschlich |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 108448, 133908, 199413, 216231 | ||
This is supposed to be fixed in portage-2.2_pre5 or earlier. This is supposed to be fixed in portage-2.2_pre5 or earlier. |
The original PORTAGE_BINHOST protocol, which is uses a remote ${PKGDIR}/All/ directory listing to download all the metadata chunks from each individual package, needs to be replaced due to inefficiency (bug #108448) and file collision issues (bug #133908). Main requirements: 1) Server side generation of a package metadata index (similar to genpkgindex from gentoolkit) to solve bug #108448. 2) Resolve package file name collisions between packages from different categories (bug #133908) Both of the above are already implemented in trunk. The package metadata index is generated as packages are built, and there is also a `emaint --fix binhost` command that can be used to update, prune, or regenerate the index. The file collisions are currently handled by using separate category directories, with no ${PKGDIR}/All directory. Anyone who would like to try the current implementation may may want to consult our "how to obtain and test development versions" doc: http://www.gentoo.org/proj/en/portage/doc/testing.xml