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 957361382C5 for ; Mon, 22 Jan 2018 04:57:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F0376E08DD; Mon, 22 Jan 2018 04:57:51 +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 5FCCEE08C8 for ; Mon, 22 Jan 2018 04:57:50 +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 9FD01335CC2 for ; Mon, 22 Jan 2018 04:57:48 +0000 (UTC) Subject: Re: [gentoo-dev] version/slot locked dependencies in eclasses like autotools.eclass and vala.eclass To: gentoo-dev@lists.gentoo.org References: From: Michael Orlitzky Message-ID: Date: Sun, 21 Jan 2018 23:57:43 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: e63f3bde-4fd7-4e9c-86db-06443b83ef4c X-Archives-Hash: 639f012cc563b655462721c40ecd20c0 On 01/21/2018 11:24 PM, Zac Medico wrote: > > Some eclasses like autotools.eclass and vala.eclass generate > version/slot locked dependencies that cause the dependencies of > inheriting ebuilds to change when the versions in the eclasses are > updated. If possible, it would be nice to avoid this version/slot > locking. If not possible, then what should be do? > This changes the deps in stable ebuilds, and was already a no-no. If the dependencies are to remain in the eclasses, then the eclasses should get a new revision when those dependencies change. Afterwards, the consumers can be revbumped and stabilized normally to utilize the new eclass. > Should we tell users to use the emerge --changed-deps=y option? Maybe > make --changed-deps=y a default setting? > Our tree shouldn't require a portage-only option to work. Besides, it's better engineering to have the one person who makes the change alert the rest of us. Having a million people poll "Did somebody change this? How about now?" constantly is silly.