On Sun, 15 Feb 2009 15:56:18 -0800 Zac Medico <zmed...@gentoo.org> wrote: > If the package manager is not able to validate a cache entry that > has been generated for an unsupported EAPI, then it will be forced > to regenerate the metadata in order to check whether or not the EAPI > has changed (example given 2 emails ago). Don't you agree that it > would be useful to be able to avoid metadata generation in cases > like this, if possible?
Well... The solution you give only *sometimes* avoids it, so it's only worth it if we expect that most EAPI changes won't mess around with inheriting at all. And given that we probably want per-cat/pkg eclasses... It only comes into its own if you expect there to be a long time between an EAPI being used in the tree and an EAPI being supported by a package manager. And even then, it's probably easier to just do a minor stable release straight away with rules for "don't know how to use this EAPI, but do know how to read metadata cache entries for it" whilst keeping new EAPI support for the next major release. Honestly, I don't think it'll be useful often enough that it's worth the added ick. -- Ciaran McCreesh
signature.asc
Description: PGP signature
