123540 – changes in kde eclasses cause a lot of metadata overhead

Bug 123540 - changes in kde eclasses cause a lot of metadata overhead

Summary: changes in kde eclasses cause a lot of metadata overhead

Status:	RESOLVED DUPLICATE of bug 108412

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-02-20 14:05 UTC by Nico Baggus
Modified:	2006-02-20 14:45 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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 ***