First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 194552
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Zac Medico <zmedico@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 194552 depends on: Show dependency tree
Bug 194552 blocks: 108448 133908 199413 210077 216231
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-10-02 20:40 0000
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

------- Comment #1 From Marius Mauch (RETIRED) 2008-03-20 18:14:53 0000 -------
This is supposed to be fixed in portage-2.2_pre5 or earlier.

------- Comment #2 From Marius Mauch (RETIRED) 2008-03-20 18:15:32 0000 -------
This is supposed to be fixed in portage-2.2_pre5 or earlier.

First Last Prev Next    No search results available      Search page      Enter new bug