On Sun, 15 Feb 2009 16:48:44 -0800 Zac Medico <zmed...@gentoo.org> wrote: > > 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. > > But how will it know if it supports those cache entries? Wouldn't > the easiest way to determine that be to have a DIGESTS version > identifier? Otherwise, the only way for it to know would be to parse > it and either throw a parse error if necessary or proceed all the > way to the digest verification step (if it doesn't hit a parse error > first).
You just need to give your package manager a way of dealing with EAPIs where it can verify that DIGESTS is correct, but not make use of the ebuild in question beyond that. Rather than having supported and unsupported EAPIs, have supported, partially-understood and unsupported EAPIs. -- Ciaran McCreesh
signature.asc
Description: PGP signature
