On 2008/06/11, Ciaran McCreesh <ciaran.mccreesh@...> wrote:

> You're missing the cases where the cache isn't usable.
> 

I was not talking about generating cache entries, and neither were you.
I've replied to you because you were suggesting that the "EAPI in
ebuilds contents" solution had extra cost when _using_ valid cache
entries (need to extract the EAPI from the ebuild before reading this
cache entry), which i think can be easily avoided.

On 2008/06/10, Ciaran McCreesh <ciaran.mccreesh@...> wrote:

> Currently we don't touch the ebuild's content *at all* for metadata
> operations, except where there's no or stale metadata cache (which is
> rare). We can get away with this currently because 0 and 1 have
> identical cache layouts and PMS has some (necessary) weasel wording;
> future EAPIs likely won't, so we're back to the chicken / egg problem.
> 
> So... We either have the EAPI from the extension (which we already
> have, since we have to read the dir to know what versions are
> available), in which case we know how to read the metadata cache file.
> Or we have to open up a file that would otherwise not be opened, just
> to parse one line so we know how to read the cache file.

-- 
TGL.
-- 
gentoo-dev@g.o mailing list