Am 22.07.2012 18:17, schrieb Vaeth: >>> I guess I'm missing some settings specific to this? I have 3 overlays >>> installed via layman, and this eix takes ridiculously long to index >>> through them, I don't know why. >>> >>> The portage tree is indexed quickly. >>> >> >> There is usually not much you can do there. This typically happens with >> overlays that contain no metadata cache. >> >> Look at your overlay directory into metadata/layout.conf. If it doesn't >> contain a "cache-formats" line you are probably out of luck since eix >> has to parse each ebuild. > > It is not the "cache-formats" line which is crucial but whether > there is an (up-to-date) metadata/cache or metadata/md5-cache > subdireectory. > If the overlay does not have such a directory (or it is not > updated regularly), You can let portage generate this directory > by using "egencache --repo=... update". > You can eix-sync automatically call this at every think > (see the example lines for eix-sync in the eix manpage). > [...] > > Actually, egencache is already *much* faster than parsing each ebuild > separately. Moreover, I guess at least with cache-format=md5-dict > it parses really only those ebuilds for which the md5 checksum has > changed (i.e. the first execution might be slow, but after updates > there is not so much delay, usually). >
Interesting. Does this interact nicely with layman or do the different VCSs barf when they find new metadata caches in their overlay directories? Regards, Florian Philipp
signature.asc
Description: OpenPGP digital signature
