| 1 |
On Wed, 11 Jun 2008 01:36:01 +0200 |
| 2 |
Thomas de Grenier de Latour <tom.gl@××××.fr> wrote: |
| 3 |
> Or you apply to future EAPI's cache formats one of the solutions that |
| 4 |
> have been proposed for the ebuild side of the very same "chicken / egg |
| 5 |
> problem": for instance, you could use $EAPI as cache filename |
| 6 |
> extension. |
| 7 |
> |
| 8 |
> And that's it, you can get EAPI from the cache, hence no more extra |
| 9 |
> reading of ebuild files, and no more perfs issues. |
| 10 |
> |
| 11 |
> It sounds so simple, am I missing something obvious? |
| 12 |
|
| 13 |
You're missing the cases where the cache isn't usable. |
| 14 |
|
| 15 |
-- |
| 16 |
Ciaran McCreesh |
Archives