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 70A881381F1 for ; Mon, 22 Jan 2018 17:00:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AF264E086D; Mon, 22 Jan 2018 16:59:42 +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 5395CE0839 for ; Mon, 22 Jan 2018 16:59:42 +0000 (UTC) Received: from pomiot (d202-252.icpnet.pl [109.173.202.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 0247E335C0C; Mon, 22 Jan 2018 16:59:39 +0000 (UTC) Message-ID: <1516640375.1256.11.camel@gentoo.org> Subject: Re: [gentoo-dev] News Item: Portage Dynamic Deps From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Cc: Zac Medico Date: Mon, 22 Jan 2018 17:59:35 +0100 In-Reply-To: <1710293.ao4jWK1sT1@pinacolada> References: <1710293.ao4jWK1sT1@pinacolada> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.6 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-Transfer-Encoding: 8bit X-Archives-Salt: 7dd57fb7-0d96-4531-9d89-258e3daf388f X-Archives-Hash: abe09b1b69f07affbf0d81f33dda2c95 W dniu pon, 22.01.2018 o godzinie 11∶28 +0100, użytkownik Andreas K. Huettel napisał: > Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico: > > > > According to Gentoo policy, future ebuild dependency changes need to be > > accompanied by a revision bump in order to trigger rebuilds for users. > > Therefore, you should only need to use --changed-deps=y for a single > > deep @world update. After that, if you encounter installed packages with > > outdated dependencies in a future deep @world update, then you should > > report it as a bug. > > Did you come up with a solution how to handle eclass-generated dependency > changes then? > > I'd loathe to have to do identical revision bumps for, say, all perl- > module.eclass consumers... > I think one of the reasons for the policy back then was to actually stop people from creating horribly broken monstrosities of eclasses. -- Best regards, Michał Górny