1 |
On Sun, 2008-11-16 at 18:38 -0600, Ryan Hill wrote: |
2 |
|
3 |
<snip> |
4 |
|
5 |
> The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the |
6 |
> latest stable ebuild of an arch without the approval of the arch team or |
7 |
> he/she will be fed to the Galrog. |
8 |
|
9 |
As long as the maintainer can pass off the maintenance of the (sometimes |
10 |
dozens) of ancient ebuilds that need to be kept around for that one arch |
11 |
to the arch team, and re-assign any resulting bugs to them, fine. Or, |
12 |
alternatively, unilaterally decide to drop all keywords for the arch in |
13 |
question. |
14 |
|
15 |
Yes, that was extreme, but no more than the previous quoted statement. |
16 |
There needs to be give and take here. Yes, it's really bad to remove |
17 |
the last stable ebuild for an arch. However, its *also* bad to have to |
18 |
maintain years old versions of lots of ebuilds. And yes, it will be a |
19 |
lot, since most packages don't exist in a vacuum, and require older deps |
20 |
(which possibly will be maintained by other maintainers than the first |
21 |
package, causing a cascade of old packages in the tree). |
22 |
|
23 |
All this will do in practice is cause maintainers to ignore bugs for |
24 |
those old packages for those few arches, since the maintainer won't have |
25 |
that version installed. In fact, in my experience, they frequently |
26 |
*can't* have that version installed, since it requires older versions of |
27 |
other packages that need to be upgraded to maintain newer versions of |
28 |
the same package. |
29 |
|
30 |
How much bit rot do we want in the tree? |
31 |
|
32 |
Daniel (who is both an arch team member and gnome team lead) |