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-51217-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1SNnoe-0003vR-0S
for garchives@archives.gentoo.org; Fri, 27 Apr 2012 16:14:40 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 84E2DE0853;
Fri, 27 Apr 2012 16:14:26 +0000 (UTC)
Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53])
by pigeon.gentoo.org (Postfix) with ESMTP id 60C1BE07D5
for <gentoo-dev@lists.gentoo.org>; Fri, 27 Apr 2012 16:13:51 +0000 (UTC)
Received: by wgbfm10 with SMTP id fm10so822501wgb.10
for <gentoo-dev@lists.gentoo.org>; Fri, 27 Apr 2012 09:13:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=20120113;
h=date:from:to:subject:message-id:in-reply-to:references:x-mailer
:mime-version:content-type;
bh=D+YgfP2NL6+bDvCeRVQV1bWFhPfHj0qizRKlN1rX4Dc=;
b=VW/zHrx4tHHd4q5wErbJARvHq3gBJS6ZzuxHrRGtOMfGFIQ/OyTg7zmN4+hx51dVJV
eRmvszcmGQNFi6OBrgSuAHcEAN/5w9sdemzkXsb/ek2aJ5TdT4gerAZew6ZRTu8wclr3
ryEWIfrXotUd39n2fqDVeXOm2MoELU4OFUNpYgUAkK9/hsyXRvGTMM5nT25p8yLpytel
TJbUx0OOeV6NX/v5WHGpnF++ffYGsCF0mk1BEgD8+VgKK3fIiiDhiqucB7Uq2Rf/wCmk
Ertq587SH/6jAnhx4ptSShRzJKcTTYuoQZV4RxvnFV715BdJR9Da+F/nwQvIYpGVYZBm
Ka4g==
Received: by 10.180.92.71 with SMTP id ck7mr7456270wib.2.1335543230549;
Fri, 27 Apr 2012 09:13:50 -0700 (PDT)
Received: from localhost (cpc13-broo7-2-0-cust130.14-2.cable.virginmedia.com. [82.9.16.131])
by mx.google.com with ESMTPS id ca3sm5431486wib.6.2012.04.27.09.13.49
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 27 Apr 2012 09:13:50 -0700 (PDT)
Date: Fri, 27 Apr 2012 17:11:24 +0100
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Making user patches globally available
Message-ID: <20120427171124.23fd8e3c@googlemail.com>
In-Reply-To: <4F9AC466.5040208@gentoo.org>
References: <20120415021641.1858ffde@gentoo.org>
<4F8A885C.3050508@gentoo.org>
<20120418185913.3d2fa68f@epia.jer-c2.orkz.net>
<201204181340.00474.vapier@gentoo.org>
<20120418184138.50153e57@googlemail.com>
<4F8F05E9.5070103@gentoo.org>
<4F8F0929.2010109@googlemail.com>
<4F8F18EC.3000707@gentoo.org>
<4F8F3513.2060202@googlemail.com>
<20120425224433.2fa0f2de@gentoo.org>
<pan.2012.04.26.06.18.31@cox.net>
<4F98EA90.4000403@gentoo.org>
<pan.2012.04.26.09.55.04@cox.net>
<4F9967DE.8000601@gentoo.org>
<pan.2012.04.26.22.08.25@cox.net>
<4F99F941.90705@gentoo.org>
<pan.2012.04.27.14.15.34@cox.net>
<20120427152709.14a6c0bf@googlemail.com>
<4F9ABE2F.8050006@gentoo.org>
<20120427164549.052d85be@googlemail.com>
<4F9AC185.1000708@gentoo.org>
<20120427170029.44eb6eb3@googlemail.com>
<4F9AC466.5040208@gentoo.org>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
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: multipart/signed; micalg=PGP-SHA1;
boundary="Sig_/209okUGoRRGFwODAj=jPlsf"; protocol="application/pgp-signature"
X-Archives-Salt: eb1f4256-d3eb-4c38-9b96-75aa213c454c
X-Archives-Hash: 64615c607199239232b122e6f5544704
--Sig_/209okUGoRRGFwODAj=jPlsf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Fri, 27 Apr 2012 09:08:06 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> > But there's no way the repoman check is going to give anything like
> > reliable answers if you're involving eclasses...
>=20
> Okay, so people who need "reliable answers" can go with your strict
> approach. Meanwhile, it's relatively easy to to a manual audit of the
> src_prepare function of each eclass.
Providing unreliable functionality just leads to whining and
contortions when it doesn't work. This isn't a situation where
compromise is necessary, so there's no reason not to just do it
properly.
--=20
Ciaran McCreesh
--Sig_/209okUGoRRGFwODAj=jPlsf
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAk+axTIACgkQ96zL6DUtXhE0dQCggOO17weP+ZjokpttkfDZwIEJ
CnMAmwREv5+QnLiewstmUL1wD/lDksHZ
=hAnT
-----END PGP SIGNATURE-----
--Sig_/209okUGoRRGFwODAj=jPlsf--