| 1 |
On Mon, Nov 10, 2008 at 12:23 PM, Mart Raudsepp <leio@g.o> wrote: |
| 2 |
> On E, 2008-11-10 at 13:13 -0500, Mark Loeser wrote: |
| 3 |
>> Removing Stable Ebuilds |
| 4 |
>> |
| 5 |
>> If an ebuild meets the time criteria above, and there are no technical issues |
| 6 |
>> preventing stabilization, then the maintainer MAY choose to delete an older |
| 7 |
>> version even if it is the most recent stable version for a particular arch. |
| 8 |
> |
| 9 |
> Even if that is a package that other packages depend on? Lets say I want |
| 10 |
> to delete an ancient version of gtk+, but arch ABC has that as the only |
| 11 |
> stable ebuild, while the rest are ~ABC. Do I remove it, as I may, and |
| 12 |
> break the whole stable tree of arch ABC, unkeyword hundreds of other |
| 13 |
> packages, or I'm just allowed to remove it but should really apply a |
| 14 |
> common sense as usual and you don't want to go into details in this |
| 15 |
> document? |
| 16 |
|
| 17 |
*MAY* choose - you don't *have* to do it - I'd prefer something along |
| 18 |
the lines of, may stablize it - if after a minimum of 30 days - maybe |
| 19 |
90 days max - if the arch team hasn't had enough time to stablize |
| 20 |
it... when will they ever? |
Archives