1 |
On Sunday 28 of March 2010 09:39:18 Ciaran McCreesh wrote: |
2 |
|
3 |
> > It's really freaking silly to wait months for stabilization of some |
4 |
> > random php/perl library that's known to work. |
5 |
|
6 |
> How do you know it works if you don't test on the arch in question? |
7 |
The problem is not waiting for some <instert some exotic arch here> to go |
8 |
stable so it would be possible to close bug and ignore arches. |
9 |
It's not about closing bug at all. |
10 |
The only inconvenience from exotic arches lagging is inability to remove |
11 |
particular old ebuild from tree, that's it. |
12 |
|
13 |
It's about having package marked stabled on my arch (amd64 in my case, may be |
14 |
other from other developer's perspective) in a timely manner. |
15 |
|
16 |
And I know it works on my arch because I test it and often use it on daily |
17 |
basis. |
18 |
|
19 |
On Sunday 28 of March 2010 13:32:59 Richard Freeman wrote: |
20 |
> amd64 has had the policy that any dev can stabilize if they've tested it |
21 |
> on a stable amd64 system, and this hasn't really caused problems. |
22 |
That would have certainly solved the problem if that policy was written and |
23 |
published anywhere. |
24 |
|
25 |
-- |
26 |
regards |
27 |
MM |