1 |
On 2008/06/11, Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
2 |
|
3 |
> You're missing the cases where the cache isn't usable. |
4 |
> |
5 |
|
6 |
I was not talking about generating cache entries, and neither were you. |
7 |
I've replied to you because you were suggesting that the "EAPI in |
8 |
ebuilds contents" solution had extra cost when _using_ valid cache |
9 |
entries (need to extract the EAPI from the ebuild before reading this |
10 |
cache entry), which i think can be easily avoided. |
11 |
|
12 |
On 2008/06/10, Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
13 |
|
14 |
> Currently we don't touch the ebuild's content *at all* for metadata |
15 |
> operations, except where there's no or stale metadata cache (which is |
16 |
> rare). We can get away with this currently because 0 and 1 have |
17 |
> identical cache layouts and PMS has some (necessary) weasel wording; |
18 |
> future EAPIs likely won't, so we're back to the chicken / egg problem. |
19 |
> |
20 |
> So... We either have the EAPI from the extension (which we already |
21 |
> have, since we have to read the dir to know what versions are |
22 |
> available), in which case we know how to read the metadata cache file. |
23 |
> Or we have to open up a file that would otherwise not be opened, just |
24 |
> to parse one line so we know how to read the cache file. |
25 |
|
26 |
-- |
27 |
TGL. |
28 |
-- |
29 |
gentoo-dev@l.g.o mailing list |