On Tue, 10 Jun 2008 19:54:33 +0530 "Arun Raghavan" <[EMAIL PROTECTED]> wrote: > Well, most file systems have a local structure for this data (=> block > group), so it's not going to be a seek that's very far. Secondly, how > many ebuilds do you need to read directly to get this data in a > typical case? Isn't this what the metadata cache is for?
It's a nice local structure when you're just using a) a nice, linear, readahead-friendly-ish slurp of the ebuild directory and b) a nice, linear slurp of files in the metadata cache, which is how things are now. When you move that to having to make alternating use of the metadata cache and the ebuild files, you're suddenly seeking backwards and forwards between two places over and over. > >> > - it heavily restricts future syntax and meaning of EAPIs > >> > >> Not by much. It's just a header. > > > > <!-- EAPI="3" --> > > Do we want to keep the spec so wide open that we support any format > under the Sun that we fancy? Seems like overgeneralizing to me. We want to keep it open enough that we're not going to have to go through yet another backwards compatibility breaking change. -- Ciaran McCreesh
signature.asc
Description: PGP signature
