From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 96854138334 for ; Thu, 10 Oct 2019 14:49:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 64CA3E08D4; Thu, 10 Oct 2019 14:49:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 00528E08C2 for ; Thu, 10 Oct 2019 14:49:30 +0000 (UTC) Received: from a1i15 (host2092.kph.uni-mainz.de [134.93.134.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ulm) by smtp.gentoo.org (Postfix) with ESMTPSA id AA99434BB13 for ; Thu, 10 Oct 2019 14:49:29 +0000 (UTC) From: Ulrich Mueller To: Subject: [gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs Date: Thu, 10 Oct 2019 16:49:20 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: a0fe9b3f-4107-42ed-8939-8dbc5a1a3f41 X-Archives-Hash: a13f713648ff9a84e3f645354814f23e --=-=-= Content-Type: text/plain Most packages in the app-emacs category have stabilize-allarches in their metadata because they are arch independent. However, their keywords don't reflect this and differ from package to package, mostly for historical reasons. So, I would like to mass keyword all ebuilds in app-emacs (as far as stabilize-allarches applies to them) to the intersection of keywords of their dependencies. Same applies to stabilisation; if an ebuild is stable on amd64, I would stabilise it on all other arches, as far as dependencies allow it. Also, any new package added to app-emacs in future would start out with the complete set of keywords. (I am aware that this doesn't agree with the policy as it is documented in the devmanual: https://devmanual.gentoo.org/keywording/index.html#keywording-new-packages) Any objections? Ulrich --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEZlHkP3TnuTbxrN0HwwkGhRxhwnMFAl2fRPAACgkQwwkGhRxh wnN5zAf7B6PEiifeVPdgiFM7VanJkgrUu+wtlUk4rGj1E+iJGOgH2ZDKHuuEadvV zI1Ag3qyJF/7cwikVRXuGcsF35T27vunH5EETM0Vp7KjemVpzRqgHFvO4iv2NBQR LTs8utMh2dbTwL2M1eYFvhKqFlGqzu4TbT/Uu+yVlv4QPOxXfoKY9beujq5HfF/Z TrR/TYXkthrdBUoHpNrfE6MX4CbSoZuljRy9qjFV6V7LPmxp2qxxj9Pzhkh3q9pt 69b180S0uySuzeMShHXWGs2tr65epUTIi/AN6uxKOXK2Brw0RmSSHa7pkaGREHww csXLLIuZfyYnpOtPKQ75+0Cy3Pk8nQ== =kAod -----END PGP SIGNATURE----- --=-=-=--