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 ) id 1NqCP3-0007o1-JT for garchives@archives.gentoo.org; Fri, 12 Mar 2010 21:28:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E09DCE0898; Fri, 12 Mar 2010 21:28:13 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id C9B3BE0887 for ; Fri, 12 Mar 2010 21:27:52 +0000 (UTC) Received: from [192.168.22.10] (ip68-4-152-120.oc.oc.cox.net [68.4.152.120]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 5EE9D1B4108 for ; Fri, 12 Mar 2010 21:27:52 +0000 (UTC) Message-ID: <4B9AB1D7.8020805@gentoo.org> Date: Fri, 12 Mar 2010 13:27:51 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.8) Gecko/20100306 Thunderbird/3.0.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] eqawarn for main tree References: <4B9A9876.8000802@gentoo.org> In-Reply-To: <4B9A9876.8000802@gentoo.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: e9f3af69-7035-49dd-b493-8f3e8b064da6 X-Archives-Hash: d342f2bcf86fcaeb39c5b9d1f73266b3 On 03/12/2010 11:39 AM, Petteri R=C3=A4ty wrote: > In eclasses there's often use for outputting QA warnings for ebuild > authors (at least in java and python could immediately make use of > this). Currently Portage has eqawarn available but it's considered > internal. Hopefully eqawarn finds it's way to the next EAPI but in the > mean while do we want: >=20 > 1) Do a wrapper like attached to eutils.eclass > 2) Use whatever e* function that seems most appropriate (for example > einfo when it's common so user LOGging setups don't get too much noise) > 3) Have a speedy next EAPI if we can find more stuff like this to bundl= e Here's another option: 4) Retroactively add eqawarn to all EAPIs and use introspection to call eqawarn only if available (and drop the introspection after about 1 year): declare -F eqawarn >/dev/null && \ eqawarn "this is ignored by older package managers" --=20 Thanks, Zac