From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-38473-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1N7buX-0007Ij-0C
	for garchives@archives.gentoo.org; Mon, 09 Nov 2009 21:36:29 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E7C65E099B;
	Mon,  9 Nov 2009 21:36:27 +0000 (UTC)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152])
	by pigeon.gentoo.org (Postfix) with ESMTP id A4DFFE099B
	for <gentoo-dev@lists.gentoo.org>; Mon,  9 Nov 2009 21:36:27 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id d23so1833246fga.10
        for <gentoo-dev@lists.gentoo.org>; Mon, 09 Nov 2009 13:36:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=UjLRaGgmRqiY/62PUiKjz0kNKGnPj1aKugryVPdQigU=;
        b=qATOt6uO5dqtDfOfbGAvdfNyLC4kVItqlWqMOUcRu662R9gsyXJSAjeerJQtZva1lx
         lpXwFEgkbDPpwjABuZJt5XOLvCrzuJWNH0RLeYDHhUlvdSpCUXNbS+zig9VlSuTNuEgn
         +u9OXSPcmQZzegJ5UUweTVv2ulbopfp7HD1w8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=QSQ/LJ2kNv7AI8mNs9hu18ig3SIisTvhINjzxLU9J/52PUP0K9VMV5MclPvzEbbZgG
         hgsmITUGvGf4kUMoTMq5W5ar9mUGOv5xRbMFMsb8ot1cD219YwVL3CZw/k3iuto4CbaM
         3cnaweRRS+wZvHUZ3rtvs+OAnu100HAn9WRJE=
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
Received: by 10.86.159.37 with SMTP id h37mr2045707fge.79.1257802587082; Mon, 
	09 Nov 2009 13:36:27 -0800 (PST)
In-Reply-To: <200911091516.28737.vapier@gentoo.org>
References: <E1N76Ny-0004jL-Q2@stork.gentoo.org>
	 <1257768532.20446.1350.camel@tablet>
	 <200911091730.27444.patrick@gentoo.org>
	 <200911091516.28737.vapier@gentoo.org>
Date: Mon, 9 Nov 2009 16:36:27 -0500
Message-ID: <deaa866a0911091336r7996f91clb197d8f207022f7d@mail.gmail.com>
Subject: Re: [gentoo-dev] QA is unimportant?
From: Robert Bradbury <robert.bradbury@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=001485e60a0d6692ae0477f6fc37
X-Archives-Salt: 3704fef6-d5e9-41ab-a5fe-c448d64d33ff
X-Archives-Hash: 39b3e1ead53b712a1fab6281de1620f9

--001485e60a0d6692ae0477f6fc37
Content-Type: text/plain; charset=ISO-8859-1

I believe QA is important from the perspective that you want to assure that
the ebuilds work.  Nothing makes a casual user more annoyed that having an
emerge for his machine fail to work.  But if you are running the emerges
unconstrained (e.g. you specify them in the keywords file) then you are
"exposed".

A recent example is the mythtv package.  It does not compile on an x86
without significant intervention (Gentoo Bug #292421).  How does it make it
into the "release" category without it compiling on the most common
machines?  (I'm dealing with an older x86 Pentium IV Prescott machine from
HP and there have to be millions of them out there in the world.).

There should be some sort of QA procedure which says "the package builds on
these minimal list of machines" before it should be released.

Then there is a separate discussion about how to best migrate people from
the "approved" packages to the cutting edge packages with some level of
warning to the user ("this may be problematic")

Robert

--001485e60a0d6692ae0477f6fc37
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I believe QA is important from the perspective that you want to assure that=
 the ebuilds work. =A0Nothing makes a casual user more annoyed that having =
an emerge for his machine fail to work. =A0But if you are running the emerg=
es unconstrained (e.g. you specify them in the keywords file) then you are =
&quot;exposed&quot;.<div>
<br></div><div>A recent example is the mythtv package. =A0It does not compi=
le on an x86 without significant intervention (Gentoo Bug #292421). =A0How =
does it make it into the &quot;release&quot; category without it compiling =
on the most common machines? =A0(I&#39;m dealing with an older x86 Pentium =
IV Prescott machine from HP and there have to be millions of them out there=
 in the world.).</div>
<div><br></div><div>There should be some sort of QA procedure which says &q=
uot;the package builds on these minimal list of machines&quot; before it sh=
ould be released.</div><div><br></div><div>Then there is a separate discuss=
ion about how to best migrate people from the &quot;approved&quot; packages=
 to the cutting edge packages with some level of warning to the user (&quot=
;this may be problematic&quot;)</div>
<div><br></div><div>Robert</div><div><br></div>

--001485e60a0d6692ae0477f6fc37--