Bug 123540

Summary:	changes in kde eclasses cause a lot of metadata overhead
Product:	Portage Development	Reporter:	Nico Baggus <mlspamcb>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	enhancement
Priority:	High
Version:	2.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Nico Baggus 2006-02-20 14:05:42 UTC

Looking into a problem why it took ages to before an emerge --sync
was (not) progressing around 50%, it appeared it is generating 
a the kde-base-eclass.cpickle for every ebuild found in that tree....
I saw it become the final size of 878000ish bytes several times.
(kde-base has more than 1500 sub modules with several ebuilds each)
Is it possible to generate the .cpickle once at the end of a branch?

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-02-20 14:45:35 UTC


*** This bug has been marked as a duplicate of 108412 ***