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 898831396D0 for ; Sat, 12 Aug 2017 10:29:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 198BDE08C3; Sat, 12 Aug 2017 10:29:48 +0000 (UTC) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 BE410E0784 for ; Sat, 12 Aug 2017 10:29:47 +0000 (UTC) Received: by mail-yw0-x236.google.com with SMTP id l82so34318979ywc.2 for ; Sat, 12 Aug 2017 03:29:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-transfer-encoding; bh=V0bAvKRmAJgblTOg+gWdZm3yAp+koPFQqcuhhJAGyTQ=; b=YQho47Zug3ArSrezkylZZzyoOuvbOXi0/bNqab7/gD+vmW0Z0UehZIqOZXA4x6JcAG CBp3YjEQeudoVUvxsSEqISG7kRIMy3ombg7QC6nkTd1VS1t/bhvGBlrbjvQ8Fjx3XSn5 Ove5yDvmx5sujYhOPD10a4EM7LqxiftrXAq5MzW6JJQke0m4DPguvDsIMV6cRqE1gBVC LPKB5r5cATudOixPoPUsJN0SHTQhLKk5CVlbb+PQTSeTXhZoFm9+g7xs+i5mBFAYJwcL ahS96hm/gNnANNb+GLRggpNrpaFxxRm0RYRBAlYT3nkqvPOT3AWsRef2ulnRSGSDbuas vMcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-transfer-encoding; bh=V0bAvKRmAJgblTOg+gWdZm3yAp+koPFQqcuhhJAGyTQ=; b=WLA9A2KXW9sCnb2ICYZ5JiHYnlsYZo16DNWKOflTnc7ui6XgXg1lznrjtj7WyOJTJY lGF9XJG/uPpDKBdLnyOaBLf/cCN2iMdG1L2u2NfODEnGVdy9BSEqNsJIYGymIzLm1klF 7sGU5+KUYDzq0MPVrEC8uZOQ4KaJo7JdaqEfVo+VNyhJkHLCCyMQs9soJZVLyslYXqqV sZmF13BvpHCpLWrXTlu+4j/gGhZy00IrbQ2UAI0YA2W1rfQYsEH3smNs0PDRgX6wP3Km uEtH4RFQFzz+fLnIfb6xo2VE2fCS0nfSGT59e36hW23zoR/mlis2gVBwUbIsyA36IBeA gR3g== X-Gm-Message-State: AHYfb5guDrO3PA+Wp9mgXUHiCcvQq1ARc8EAmvzp8WbsBAapAdabuBFv B/0f7jx4sC7p7V8YLA9SSjHkwIyAftDx X-Received: by 10.37.53.67 with SMTP id c64mr14379589yba.320.1502533786360; Sat, 12 Aug 2017 03:29:46 -0700 (PDT) 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 Sender: freemanrich@gmail.com Received: by 10.129.71.3 with HTTP; Sat, 12 Aug 2017 03:29:45 -0700 (PDT) In-Reply-To: <4ebddcf6-1d84-684a-6e3c-96bb65c24fd2@gentoo.org> References: <1502521423.1045.0.camel@gentoo.org> <4ebddcf6-1d84-684a-6e3c-96bb65c24fd2@gentoo.org> From: Rich Freeman Date: Sat, 12 Aug 2017 06:29:45 -0400 X-Google-Sender-Auth: P-gm0NMvgN-vgh3pnUX9-VZQ7KA Message-ID: Subject: Re: [gentoo-dev] Revisions for USE flag changes To: gentoo-dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 3cff8d4e-bfe5-4329-b487-4220c8b5e518 X-Archives-Hash: 4f10569b1f606b94903db254341057d3 On Sat, Aug 12, 2017 at 5:57 AM, Michael Orlitzky wrote: > On 08/12/2017 03:03 AM, Micha=C5=82 G=C3=B3rny wrote: >> >> Please provide some examples of recent in-place USE changes that benefit >> from revbumps. >> > > There is no single example. Things only get simpler if *all* USE changes > come with a new revision. > My gut feeling is that the change you want is probably a good thing, but it will never happen if you can't provide a single example of something bad happening due to the lack of a revbump. The easy counter-argument to your suggestion is "if it ain't broke, don't fix it." As others have pointed out, the portage flags are useful even if we make this change, so they're not going away. Also, I don't see any portage maintainers saying that they want this change, or that they'll remove any code if this change is made. The only potential benefit I see is QA. However, I've been running with --changed-use for eons (and was running with --newuse before that) so I couldn't tell you what happens in practice when you don't use those settings. This policy change would make my life easier, because for big packages it would encourage maintainers to not make IUSE changes until they do revbumps, which would save me a build. I'm running on relatively old hardware at this point so these rebuilds actually do cost me quite a bit of time. I'm not sure that not using --changed-use is a great option though as it will make it that much harder to keep things consistent when I do modify my package.use/make.conf. --=20 Rich