| 1 |
2012/12/13 Jory A. Pratt <anarchy@g.o>: |
| 2 |
> |
| 3 |
> As many of us are aware the tree is growing to a size that is really |
| 4 |
> unacceptable for many. We have many packages that have excessive amounts |
| 5 |
> of versions laying around that are not used any more. Many of these |
| 6 |
> packages with excessive revisions most likely do not work with modern |
| 7 |
> code any longer, or have security exploits or just dead upstreams that |
| 8 |
> do not support them any longer that have been replaced with newer |
| 9 |
> packages. Well these packages are around for stable at the moment when a |
| 10 |
> newer package replaces the old and makes stable branch we need to remove |
| 11 |
> the dead package. This is nothing but an attempt to start reducing the |
| 12 |
> size of the tree and supported packages as a whole to improve the |
| 13 |
> quality of Gentoo as a WHOLE. All packages of course need to be handled |
| 14 |
> in a manner that works with maintainers/herd and the community as a whole. |
| 15 |
> |
| 16 |
> Jory |
| 17 |
> |
| 18 |
> |
| 19 |
Please press enter more often when sending mails :P So we can in-post |
| 20 |
rather than bottom/top post to your mails. |
| 21 |
|
| 22 |
I totaly agree that we should reduce amount of versions we provide in |
| 23 |
main tree and I tried to adhere to this policy in all herds I am |
| 24 |
member of or whenever I found some insane stuff in cvs. |
| 25 |
|
| 26 |
But there is one big ass but. We have some packages that were |
| 27 |
stabilised last time few year back and they provide multiple testing |
| 28 |
versions on top of that. |
| 29 |
Who is the one to deterimine which one should go stable and which to get rid of? |
| 30 |
We had some humble tryouts to create automatic stabilisation request |
| 31 |
which didn't turn out exactly well as most of the maintainers had to |
| 32 |
actually do more work ;-) |
| 33 |
|
| 34 |
|
| 35 |
Long story short for to have some sane policy wrt amounts of the |
| 36 |
stable packages. Testing packages can't be handled easily by some rule |
| 37 |
because the development differs everywhere. |
| 38 |
Packages should provide only one stable version per branch/slot by default. |
| 39 |
Exception for this rule are base-system packages where requirement is |
| 40 |
to provide two stable versions at any given time. |
Archives