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 575C213997D for ; Fri, 15 Nov 2019 12:29:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8A969E0835; Fri, 15 Nov 2019 12:29:15 +0000 (UTC) Received: from smtp.gentoo.org (dev.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 3FB42E0826 for ; Fri, 15 Nov 2019 12:29:15 +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 22B9E34CE6E for ; Fri, 15 Nov 2019 12:29:14 +0000 (UTC) Subject: Re: [gentoo-dev] Why adding python3_8 to Gentoo sucks? To: gentoo-dev@lists.gentoo.org References: <4798502.u5CIKBo2SD@t490> <7b0a4f20cb73bbbd7acb3e1efd7fe9f541ccd2cf.camel@gentoo.org> <4009341.1O8DcbvQnu@t490> From: Michael Orlitzky Message-ID: Date: Fri, 15 Nov 2019 07:29:11 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 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 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: c875b0ac-2c4e-404f-9634-8a74ed4f38f5 X-Archives-Hash: d26a25a4fffc97f704bd9a7f0c72c563 On 11/15/19 7:22 AM, Michał Górny wrote: > > https://devmanual.gentoo.org/general-concepts/ebuild-revisions/index.html > Two things on that page are outright wrong: 1. If the package has stable keywords, they should be moved to the new revision without dropping. To commit the ebuild, repoman commit --straight-to-stable option should be used. That violates our other stabilization policies and common sense. 2. Examples of changes that can be done without a revision bump are... adding a new USE flag or removing an existing one (since change in USE flags is going to trigger --changed-use rebuild), The --changed-use flag is not default, not part of the PMS, and slows portage down even more than it already is. The council ratified the PMS and the associated GLEP, and following this advice breaks PMS-compliant package managers.