On Wed, Jun 11, 2008 at 12:06 PM, Ciaran McCreesh <[EMAIL PROTECTED]> wrote: > On Wed, 11 Jun 2008 08:31:45 +0200 > Thomas de Grenier de Latour <[EMAIL PROTECTED]> wrote: >> On 2008/06/11, Ciaran McCreesh <[EMAIL PROTECTED]> 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. > > And it does, since EAPI has to be known to use the cache contents. The > way it's handled currently is a hack that doesn't work with future EAPIs > defining new metadata.
Fix that, then. And I understand that the code is already there in both portage and pkgcore to store the cache as key-value pairs rather than one-slot-per-key, and would be relatively trivial to add to paludis. Regards, -- Arun Raghavan (http://nemesis.accosted.net) v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com -- gentoo-dev@lists.gentoo.org mailing list
