Petteri Räty a écrit :
Peter Volkov kirjoitti:
May be we should punt them from the tree?
Eclasses can't be removed...
Arguably we could specify a time period before they can be removed? This
is probably GLEP material though :)
Maybe we should have a deprecated eclass for showing a common messaged
that certain eclasses should not be used. Then deprecated eclasses could
be detected by looking if they inherit deprecated.
Maybe we could just extend the eclass API to have a
DEPRECATED="yyyy-mm-dd" variable at the top of the eclass - which would
move the burden to the PM - instead of adding yet another eclass (which
we wouldn't be able to remove :p)
Cheers
--
Rémi Cardona
LRI, INRIA
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
[email protected] mailing list
