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 109471396D0 for ; Sat, 12 Aug 2017 05:03:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 66FCC1FC019; Sat, 12 Aug 2017 05:02:55 +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 1F8B21FC005 for ; Sat, 12 Aug 2017 05:02:54 +0000 (UTC) Received: from [IPv6:2001:980:4ed9:1:beae:c5ff:fe48:18dc] (unknown [IPv6:2001:980:4ed9:1:beae:c5ff:fe48:18dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: graaff) by smtp.gentoo.org (Postfix) with ESMTPSA id AB24D341A80 for ; Sat, 12 Aug 2017 05:02:53 +0000 (UTC) Message-ID: <1502514169.32531.18.camel@gentoo.org> Subject: Re: [gentoo-dev] Revisions for USE flag changes From: Hans de Graaff To: gentoo-dev@lists.gentoo.org Date: Sat, 12 Aug 2017 07:02:49 +0200 In-Reply-To: References: Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-6NVP2NVWhkPCrqeb6Ltl" X-Mailer: Evolution 3.22.6 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 X-Archives-Salt: a34be5d0-0d70-433c-af4f-c8b56fe72ba4 X-Archives-Hash: e772e730fe77316be74d0671554cfdbd --=-6NVP2NVWhkPCrqeb6Ltl Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2017-08-11 at 19:50 -0400, Michael Orlitzky wrote: >=20 > =3D=3D New revisions for USE flag changes =3D=3D >=20 > I suggest that in hindsight, we can do better. Not all IUSE changes are equal and thus a policy that treats them all the same doesn't make sense to me. Maintainers are in a better position to judge whether or not a new revision is needed.=20 > =3D=3D tl;dr =3D=3D >=20 > We would be better off with respect to IUSE changes and revisions if > we > deleted the --changed-use and --newuse flags right now, and just > required developers to revbump when changing IUSE. I don't see how these flags can be removed. You are describing a policy, but this won't change the fact that IUSE changes are still technically possible and will still happen, intentional or otherwise. Hans --=-6NVP2NVWhkPCrqeb6Ltl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iHUEABEIAB0WIQSx3yP+V82AqODatGmIg/pWowio1wUCWY6L+QAKCRCIg/pWowio 1+AAAP9omchfdxV0aoQr6TE8fMiAHanoNYveG6YFSBTRDMghKwD+Ohu9/qjotEmz ArVMbPRaXMvObPKWP96En0Z5bVjZURk= =xIDy -----END PGP SIGNATURE----- --=-6NVP2NVWhkPCrqeb6Ltl--