| 1 |
On Mon, 18 Feb 2008 15:43:56 -0500 |
| 2 |
Doug Klima <cardoe@g.o> wrote: |
| 3 |
> Ok. I guess no one else has any feelings about this. |
| 4 |
> |
| 5 |
> Potentially doing something like: |
| 6 |
> |
| 7 |
> DEPRECIATED="$DEPRECATED $ECLASS" |
| 8 |
|
| 9 |
Deprecated != depreciated. |
| 10 |
|
| 11 |
> at the top of each deprecated eclass. In the end $DEPRECATED would |
| 12 |
> have a list of all the eclasses that are deprecated? |
| 13 |
> |
| 14 |
> Maybe even: |
| 15 |
> |
| 16 |
> DEPRECATED_MYECLASS="myreplacement" |
| 17 |
> |
| 18 |
> would mean that myeclass.eclass is replaced by myreplacement.eclass ? |
| 19 |
|
| 20 |
Well, that depends upon whether you want it to be part of the C/P-V |
| 21 |
metadata... If you do, it's a cache format change (and you can't easily |
| 22 |
do DEPRECATED_*). But then, deprecation is a property of the eclass, |
| 23 |
not an C/P-V. |
| 24 |
|
| 25 |
-- |
| 26 |
Ciaran McCreesh |
Archives