From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-59264-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 84A72138010
	for <garchives@archives.gentoo.org>; Sun, 24 Mar 2013 14:35:28 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id C061DE07D1;
	Sun, 24 Mar 2013 14:35:25 +0000 (UTC)
Received: from foo.stuge.se (foo.stuge.se [212.116.89.98])
	by pigeon.gentoo.org (Postfix) with ESMTP id 78637E0648
	for <gentoo-dev@lists.gentoo.org>; Sun, 24 Mar 2013 14:35:24 +0000 (UTC)
Received: (qmail 19574 invoked by uid 501); 24 Mar 2013 14:35:22 -0000
Message-ID: <20130324143522.19573.qmail@stuge.se>
Date: Sun, 24 Mar 2013 15:35:22 +0100
From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-text/cuneiform
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <514CE32C.7090509@gentoo.org> <m3ehf5evw7.fsf@carbon.jhcloos.org> <CAG2jQ8jdRk6itGb2Ro_wNmaHO1KCKWJL4HD_-gboxrFJLiD8oA@mail.gmail.com> <m3y5dddgcz.fsf@carbon.jhcloos.org> <CAAr7Pr9UD_A_CM4v29wjVcm01NxBGrEtAg1DV0U62Pz=_nK9jA@mail.gmail.com> <20130324132456.13752.qmail@stuge.se> <CAGfcS_=R53K+e9jtJXog0XxExA1dtLQwaJfL3PL-LJ7gLz1nOg@mail.gmail.com> <20130324135232.15911.qmail@stuge.se> <CAGfcS_=DSdPpbv-M6yme=5Vcb2DtVCxvA6BYdSUXUe=vwmwsSw@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGfcS_=DSdPpbv-M6yme=5Vcb2DtVCxvA6BYdSUXUe=vwmwsSw@mail.gmail.com>
X-Archives-Salt: 907af7c7-401c-4412-b9dc-0fae15b33625
X-Archives-Hash: 6647883f56455e15e7e2df23f027c1b5

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