From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A1D8313877A for ; Thu, 17 Jul 2014 14:09:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DCA0AE0925; Thu, 17 Jul 2014 14:09:39 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F2A98E08E9 for ; Thu, 17 Jul 2014 14:09:38 +0000 (UTC) Received: from [192.168.1.160] (CPE002401f30b73-CM78cd8ec1b205.cpe.net.cable.rogers.com [99.224.181.112]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id A463733FC8D for ; Thu, 17 Jul 2014 14:09:37 +0000 (UTC) Message-ID: <53C7D916.2040709@gentoo.org> Date: Thu, 17 Jul 2014 10:09:26 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 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] Prevent to need to change all keywords at the same time References: <1405600131.895.14.camel@gentoo.org> In-Reply-To: <1405600131.895.14.camel@gentoo.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 6715d10c-daab-4225-bf8c-8074de033135 X-Archives-Hash: 2a3ca0eef0db778bbb6a3dba47378ebb -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 17/07/14 08:28 AM, Pacho Ramos wrote: > I recently noticed this: > https://bugs.gentoo.org/show_bug.cgi?id=502836 > > imlib2 ebuild can only be stabilized in one round for all arches > as KEYWORDS are set in eclass depending on E_STATE="release". That > has an important drawback as forces all arches to be done at the > same time and, since some are much slower than others, forces all > to wait for them. And, as that can depend on even more > stabilizations (like it's the case) all that bugs blocking the > stabilization need to also be done for *all* arches before. > > I am not sure if any policy exists for this, but I would forbid to > make this due this issue. I would instead move to use KEYWORDS en > ebuild as done usually. > > What do you think? > > Unless there is some sort of need to synchronize stable keywords across multiple packages in an identical fashion, that is -so important- it can't be left to AT's and maintainers to ensure the stablereq bugs are filed across them all at once on their own, I don't see a reason for setting KEYWORDS in an eclass. So, +1 for moving KEYWORDS to ebuilds. I'm not sure if "forbidding" is necessary, as I think strongly discouraging all overly-complicated solutions like this one would suffice. (and yes i know the irony of this statement given that I'm in the gx86-multilib project :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPH2RYACgkQ2ugaI38ACPCq3gD7B0Sf5QEs3PUSLfjIywP4HPp6 wkKHXP/i3/1N846wH8YA/0h+4yWByW6AmKS6ii+ZGwvy6W/HwowMnXOGOMPgtBux =zS/0 -----END PGP SIGNATURE-----