Rich Freeman wrote:
> > A per-ebuild bug metric would be cool. A kind of health indicator
> > for individual ebuilds, alerting users when some of our installed
> > ebuilds go yellow, so that we have perhaps on the order of six
> > months before the package goes red, at which point it would be fine
> > to mask at will. Does that make sense?
> 
> And how would users actually be alerted?

The when I think is after emerge --sync.

The how may not be as easy. :)

Maybe the bug metric can be added into portage easily enough,
allowing it to be transfered as part of sync. I think that would be
ideal.


> Seems like a potentially interesting GCOC project, but somebody
> does need to actually implement this for it to be useful...

Sure, but an idea of what to accomplish is a good start.


//Peter

Reply via email to