| 1 |
On 7/27/06, Chris Gianelloni <wolf31o2@g.o> wrote: |
| 2 |
> Honestly, they shouldn't be stable. In fact, likely, many shouldn't be |
| 3 |
> in the tree. We have way too many packages that are used solely by a |
| 4 |
> small group of people sitting around the tree. These would be better |
| 5 |
> served in official overlays, where they can be maintained by the |
| 6 |
> interested parties (including users), rather than in the tree. |
| 7 |
|
| 8 |
This might be a good idea. I think some additional tools support |
| 9 |
would be useful, so that things like esearch could find things in the |
| 10 |
official overlays that are not actually present on the user's system. |
| 11 |
|
| 12 |
> The "majority" of packages are also the ones that need more extensive |
| 13 |
> testing. Sure, we could probably stabilize a bunch of the fringe |
| 14 |
> packages that hardly anyone uses and it wouldn't affect anything. |
| 15 |
|
| 16 |
The majority of Aliz's database seems to be made up of these "fringe" |
| 17 |
packages. Many of which are stable on at least one arch already, or |
| 18 |
have only a single version in the tree anyway. Stabilizing these on |
| 19 |
the remaining archs that they support should not have any significant |
| 20 |
impact on the perceived overall quality of Gentoo. |
| 21 |
|
| 22 |
> Another problem is that we don't *know* what is being run by our users. |
| 23 |
> This is something that the Summer of Code project for a Gentoo Stats |
| 24 |
> project should at least help with, as it will give us an insight into |
| 25 |
> what is actually being used and what isn't. |
| 26 |
|
| 27 |
I hope that all users subscribe to this, it will only be useful with a |
| 28 |
large enough pool of people submitting their stats. It would also be |
| 29 |
great if Aliz's database incorporated this information when it becomes |
| 30 |
available. |
| 31 |
|
| 32 |
> Seriously, folks. If you think that packages should be available |
| 33 |
> faster, run ~arch. Test the packages. Report successes/failures to the |
| 34 |
> maintainers. File stabilization bugs if your favorite package hasn't |
| 35 |
> had another bug in 30 days and you've been using it. Basically, help |
| 36 |
> out, rather than sitting back and complaining. Complaining helps |
| 37 |
> nobody. |
| 38 |
|
| 39 |
Please don't interpret my original message as a complaint. It isn't. |
| 40 |
It is mostly a question of the process. My understanding of |
| 41 |
stabilization bugs was that they should be the exception, not the |
| 42 |
rule... |
| 43 |
|
| 44 |
> that you might not be able to make a commitment, or even want to do so. |
| 45 |
> However, every single bug report that you file *is* helping out... and |
| 46 |
> every little bit helps. |
| 47 |
|
| 48 |
...and I was wrong. |
| 49 |
|
| 50 |
Regards, |
| 51 |
-Richard |
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives