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 C5EA01382C5 for ; Mon, 22 Jan 2018 08:24:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE60DE094A; Mon, 22 Jan 2018 08:24:49 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 6F074E092D for ; Mon, 22 Jan 2018 08:24:49 +0000 (UTC) Received: from localhost (unknown [IPv6:2a01:e34:eeaa:6bd0:4ecc:6aff:fe03:1cfc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id 9ED69335C0A; Mon, 22 Jan 2018 08:24:47 +0000 (UTC) Date: Mon, 22 Jan 2018 09:24:40 +0100 From: Alexis Ballier To: Zac Medico Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] News Item: Portage Dynamic Deps Message-ID: <20180122092440.5fa55cf5@gentoo.org> In-Reply-To: References: Organization: Gentoo X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: a0467a89-b9de-4866-9b81-b012b57f5025 X-Archives-Hash: 3053d2c48469cf55a2f98b948ee2ad8a On Sun, 21 Jan 2018 23:01:08 -0800 Zac Medico wrote: > Please review. > > Title: Portage Dynamic Deps > Author: Zac Medico > Posted: 2018-01-28 > Revision: 1 > News-Item-Format: 2.0 > Display-If-Installed: > Beginning with Portage 2.3.20, the previous default --dynamic-deps=y > setting has changed to --dynamic-deps=n. Due to this change, some > users may experience emerge dependency calculation failures triggered > by installed packages that have outdated dependencies. In order to > avoid problems of this nature, use the emerge --changed-deps=y option > with your next deep @world update. What's the rationale behind this ? What I mean is: while '--dynamic-deps=n --changed-deps=n' is the technically correct behavior, this just seems like throwing unbearable dep calculation failure messages at users' faces while we could default to '--dynamic-deps=n --changed-deps=y' and get the already policy-mandated behavior of 'force a rebuild when you change deps'.