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... -- Andreas K. Hüttel [email protected] Gentoo Linux developer (council, toolchain, perl, libreoffice, comrel)
signature.asc
Description: This is a digitally signed message part.
