| 1 |
Ulrich Mueller wrote: |
| 2 |
> In last week's council meeting a policy for removal of old eclasses |
| 3 |
> has been defined: |
| 4 |
> ,---- |
| 5 |
> | The council voted that to remove eclasses devs should take the |
| 6 |
> | following steps: |
| 7 |
> | 1) Deprecate eclasses. |
| 8 |
> | 2) Removal of all functionality relating to installing. |
| 9 |
> | 3) After two years the eclass may be removed. |
| 10 |
> `---- |
| 11 |
> |
| 12 |
> A quick scan shows that the following eclasses were deprecated more |
| 13 |
> than three years ago, and are used by no ebuild in the tree: |
| 14 |
> |
| 15 |
> 2002-05-25 inherit.eclass |
| 16 |
> 2003-12-11 kde-i18n.eclass |
| 17 |
> 2004-04-16 koffice-i18n.eclass |
| 18 |
> 2005-09-18 jakarta-commons.eclass |
| 19 |
> 2006-02-28 php.eclass |
| 20 |
> 2006-02-28 php-2.eclass |
| 21 |
> |
| 22 |
> Do we want to remove any of these? Have I missed other candidates? |
| 23 |
> |
| 24 |
> Ulrich |
| 25 |
> |
| 26 |
|
| 27 |
I would say that we should remove eclasses at earliest two years from |
| 28 |
now. The benefit from removing now is near zero and there's some people |
| 29 |
lurking around that haven't updated in ages. |
| 30 |
|
| 31 |
Regards, |
| 32 |
Petteri |
Archives