On Sat, 2009-05-16 at 20:21 +0100, Ciaran McCreesh wrote: [...] > Can't do that. The package manager has to barf on unrecognised .ebuild > files.
I assume the reasons are the same as below. > > If this is not viable, make an unrecognised version string cause the > > same fallback as an unsupported EAPI => ignore the ebuild. Again, fast > > track to stable portage, and not so long after, you're done. > > Again, no good. First, it means a year or more wait before doing > anything. Second, it removes a whole level of error checking. Third, it > means a package manager can't know what versions are available for a > package without generating metadata for every potential version. 1) Why a year? I'd say 4-6 months after portage goes stable is fine. 2) Replace the errors with warnings. And these need to exist only at 'repoman manifest' time, so they're not end-user-visible (and don't need to be). -- Arun 3) This is again, when the metadata is uncached, which is not the normal case and can be ignored. And the (minor) performance penalty in the cached case, if any, is not reason enough to make this change.
signature.asc
Description: This is a digitally signed message part
