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 08EE61396D0 for ; Sun, 13 Aug 2017 16:12:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68AC7E0DA6; Sun, 13 Aug 2017 16:12:47 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.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 1B9F2E0D97 for ; Sun, 13 Aug 2017 16:12:46 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id B4C1F341722 for ; Sun, 13 Aug 2017 16:12:45 +0000 (UTC) Subject: Re: [gentoo-dev] Revisions for USE flag changes To: gentoo-dev@lists.gentoo.org References: <20170813160625.GA29656@linux1.home> From: Michael Orlitzky Message-ID: Date: Sun, 13 Aug 2017 12:12:39 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.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: <20170813160625.GA29656@linux1.home> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 00463192-6b75-4b33-9856-7909ae4a3612 X-Archives-Hash: 14c089a5b64fd821f09255682e6ecb77 On 08/13/2017 12:06 PM, William Hubbs wrote: > > There is a down side you didn't talk about -- more work for the arch > teams and for us in terms of stabilizations. > > When we revbump, a new revision automatically gets ~ keywords on all arches > unless we make an exception. If a revision changes iuse but could still > be built with the stable tree, I would want to be able to commit this > type of revision directly to stable. > I don't think you should be adding features and code to stable ebuilds in the first place, but if you're going to do it, then I wouldn't let a little -r1 on the end of the filename stop you =P