On Tue, Jan 23, 2018 at 7:40 AM, Michael Palimaka <[email protected]> wrote: > On 01/22/2018 09:28 PM, Andreas K. Huettel wrote: >> 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? > > No. > > Bug #641346 was filed for clarification about this, but it just got > closed without answering the question or consulting anyone.
>From the bug: "I don't see the need for anything further before the default behavior can be changed in portage, I'm all for it matching PMS behavior." (More details in the comment.) The question was "I would like to ask Council to state more precisely what needs to be specifically documented before we can stop enabling dynamic-deps in Portage by default." So, the answer to the question appears to be "nothing." That might not be an answer that you like, but it is an answer. I can't vouch for who was or wasn't consulted before it was given. -- Rich
