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 C90D5138262 for ; Fri, 20 May 2016 12:38:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 987DA224078; Fri, 20 May 2016 12:38:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 831A7224050 for ; Fri, 20 May 2016 12:38:17 +0000 (UTC) Received: from [10.100.0.6] (host-37-191-220-247.lynet.no [37.191.220.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: k_f) by smtp.gentoo.org (Postfix) with ESMTPSA id D21E5340B57 for ; Fri, 20 May 2016 12:38:15 +0000 (UTC) Subject: Re: [gentoo-dev] new developers' keyword requests References: <20160519165130.7e9bc385@wim.fritz.box> To: gentoo-dev@lists.gentoo.org From: Kristian Fiskerstrand Message-ID: <550ab3a6-1a4b-fa19-b111-5cbf82fe597e@gentoo.org> Date: Fri, 20 May 2016 14:38:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.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 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4X1rcvN21jMGB6oW1fIxrxp3gksMj2Q2T" X-Archives-Salt: 1d41a086-eb8d-4f51-a1f3-4f355551f9c0 X-Archives-Hash: 1e39979bf63af262204ab7069f465913 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4X1rcvN21jMGB6oW1fIxrxp3gksMj2Q2T Content-Type: multipart/mixed; boundary="iMxreQsp1wfBMA3o7mKdG7NqwCeHLg8Cu" From: Kristian Fiskerstrand Reply-To: k_f@gentoo.org To: gentoo-dev@lists.gentoo.org Message-ID: <550ab3a6-1a4b-fa19-b111-5cbf82fe597e@gentoo.org> Subject: Re: [gentoo-dev] new developers' keyword requests References: <20160519165130.7e9bc385@wim.fritz.box> In-Reply-To: --iMxreQsp1wfBMA3o7mKdG7NqwCeHLg8Cu Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 05/20/2016 03:36 AM, Daniel Campbell wrote: > On 05/19/2016 07:51 AM, Jeroen Roovers wrote: =2E. >> > To make sure I understand what you're getting at, are you saying some > devs get on board and then request to add keywords to packages that the= y > already maintain? If said arches are already supported in Gentoo I see > little problem with that, especially if they intend on being part of th= e > arch testing team for that arch or have access to the hardware. Can you elaborate on your definition of supported in this case? does it deviate from stable arches (alpha, amd64, arm, hppa, ia64, ppc, ppc64, sparc, x86)? >=20 > But if this is a case of developers asking for arch keywords to be adde= d > for arches that aren't (yet) supported in Gentoo, I agree that we need > some sort of formal requirements, much like we do for stabilization (30= > days no bugs, etc). Covering it in the devmanual is a great idea. keywording for a new arch should normally only be done when necessary, mainly if it is a direct dependency of another package. There is no need to keywor it for an arch until it has been tested on that arch by some user / developer ... certainly not because some committing developer think it is nice to have all arches listed just in case. It is actually already [covered in the devmanual]; " It's important to note that alternative arches (like alpha, ia64, s390, sh, sparc, hppa, ppc*) are mainly undermanned arches, some of them are slow, they have more basic problems and have a small userbase. Just file bugs for these architectures when a package is going to be a dependency of a package already keyworded. " >=20 > But adding keywords, as we know, comes with maintenance burden. New Indeed, more people should think of this. Adding packages in itself adds maintenance burdens for other teams and the usefulness should be considered accordingly before doing so > arches can't get supported without people active in the community and > actually using the hardware. If that interest isn't there, why should w= e > add the keywords to the main repo? Overlays may be a fine alternative. >=20 > Just my 2=C2=A2. Thanks for bringing this up, it's a topic I didn't kno= w was > a concern. >=20 References: [covered in the devmanual] https://devmanual.gentoo.org/keywording/index.html --=20 Kristian Fiskerstrand OpenPGP certificate reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 --iMxreQsp1wfBMA3o7mKdG7NqwCeHLg8Cu-- --4X1rcvN21jMGB6oW1fIxrxp3gksMj2Q2T Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJXPwUwAAoJECULev7WN52FuA8H/RLX16RWQxJBFDJOIN/zcG/U UK0XYJN9g/BDgAjWbMlIim9cujtFEbqQln0WRQ92voaT0ysw2EK42Aro8+Qzfm4i fDdgiZt/SecZD8yWCVnq6Is1kp/VBXW0oNvLgj0GASaHiFrqMhfTCKzplFi0ZRGx h2tvaLj48OxzlQFXBle0yo3X0HkDJ478Jmww3gfgsl6ypfiDctQ4ExXAdh/hHAN9 U+5FOmkAUz4mi0arfCBsJ8ogbkQomo0H7phYwv0PnLCeD3FhOzXTNppDCQgI+Xs2 iJvDOeIUq1Tyv+l7Ra7Ns69blDMZFcVucl4VXdBeUUEUxFcQGsU2F7KUiyAYTyQ= =BZSk -----END PGP SIGNATURE----- --4X1rcvN21jMGB6oW1fIxrxp3gksMj2Q2T--