Summary: | emerge sync (in Portage 2.0.51.22-r3) took too much time in updating kde-base-eclass.cpickle | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Honza <hkmaly> |
Component: | Enhancement/Feature Requests | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Honza
2005-12-20 01:13:42 UTC
Try this patch (run emerge metadata after applying). http://dev.gentoo.org/~ferringb/portage/2.0/3.0-cache-backport-experimental-7.patch Closing LATER. Hey ! What is cache.cache_errors ? Hmmm ... don't you forgot to add something like copying some files to /usr/lib/portage/pym/cache ? I hope it's only think you forgot ... Yes, it feels much faster and steadier. I'll try to make some benchmarks later to have real numbers. (In reply to comment #2) > Hey ! What is cache.cache_errors ? > > Hmmm ... don't you forgot to add something like copying some files to > /usr/lib/portage/pym/cache ? I hope it's only think you forgot ... I see no errors, using this patch myself. I assume that anyone who tests this patch knows how and where to apply this. If not, then better don't mess with portage. ;) You mean it's not supposed to be applied while emerging portage ? |