| 1 |
Rich Freeman wrote: |
| 2 |
> > A per-ebuild bug metric would be cool. A kind of health indicator |
| 3 |
> > for individual ebuilds, alerting users when some of our installed |
| 4 |
> > ebuilds go yellow, so that we have perhaps on the order of six |
| 5 |
> > months before the package goes red, at which point it would be fine |
| 6 |
> > to mask at will. Does that make sense? |
| 7 |
> |
| 8 |
> And how would users actually be alerted? |
| 9 |
|
| 10 |
The when I think is after emerge --sync. |
| 11 |
|
| 12 |
The how may not be as easy. :) |
| 13 |
|
| 14 |
Maybe the bug metric can be added into portage easily enough, |
| 15 |
allowing it to be transfered as part of sync. I think that would be |
| 16 |
ideal. |
| 17 |
|
| 18 |
|
| 19 |
> Seems like a potentially interesting GCOC project, but somebody |
| 20 |
> does need to actually implement this for it to be useful... |
| 21 |
|
| 22 |
Sure, but an idea of what to accomplish is a good start. |
| 23 |
|
| 24 |
|
| 25 |
//Peter |
Archives