Pandu Poluan <pa...@poluan.info> wrote: >> > I was thinking: is it feasible, to "precalculate" the dependency tree? >> >> I thought that's what the portage cache does, as far as it can. > > Well, AFAIK, portage needs to kind of simulate everything going on in an > ebuild to get the list of dependencies/blockers... If this can be > 'pre-simulated' resulting in a simpler to parse 'database' of > dependencies...
This *is* the portage cache: Execute e.g. cat /usr/portage/metadata/md5-cache/sys-apps/portage-9999 You see that DEPEND, RDEPEND, PDEPEND are readily available. If metadata/md5-cache should not be up-to-date (e.g. if you use an overlay without that data and without calling egencache), portage generates a similar cache in /var/cache/edb/dep (checksums and/or filestamps are used to verify that the caches are up-to-date - this also takes somewhat time but not very much and cannot be avoided to guarantee correct behaviour).
