On 02/27/2018 12:05 PM, Ian Zimmerman wrote: > > When I read this, I realize I don't understand the difference between > these two options. Or to be more accurate, I know that --deep means > looking at dependencies beyond the first level; but isn't that just a > superset of those found by --changed-deps?
You're right about --deep. The --changed-deps flag, on the other hand, is a crutch for when developers make in-place edits to ebuilds and don't make the necessary revision bump. The revision bump is required, but sometimes people forget or are just assholes and don't care that this is a huge hassle for end users. When you use --changed-deps, portage scans the tree for those sorts of mistakes, and rebuilds the packages that have been changed in-place, without regard to where in the dependency graph they lie.
