Ciaran McCreesh kirjoitti:
On Mon, 18 Feb 2008 17:19:55 -0500 Doug Klima <[EMAIL PROTECTED]> wrote:Well, that depends upon whether you want it to be part of the C/P-V metadata... If you do, it's a cache format change (and you can't easily do DEPRECATED_*). But then, deprecation is a property of the eclass, not an C/P-V.Deprecation is a property of the eclass. Not of an ebuild. The point is to allow utilities and users/developers to clearly see that an eclass is deprecated and what they should be using in place of it.Right. eclasses don't currently have metadata (and there's no easy way for them to have it, since eclasses can't be sourced standalone). If you make deprecation a metadata variable, there will be no way for a package manager to determine whether an eclass is deprecated unless it has an ebuild that uses that eclass. Is this a satisfactory restriction?
A metadata.xml like file for eclasses could fit the bill. It could have both the maintainer info and the deprecation information among other things.
Regards, Petteri
signature.asc
Description: OpenPGP digital signature
