On 27/09/2015 17:12, Mike Gilbert wrote: > On Sun, Sep 27, 2015 at 11:07 AM, Alan McKinnon <[email protected]> > wrote: >> So, my question: wtf are dynamic deps? How do I find the records they >> must leave behind in portage? > > For the latter question, you can rebuild affected packages like so: > > emerge --with-bdeps=y @changed-deps. > > You can also add --changed-deps to your emerge command line for world updates. >
Thanks. Running that gives surprising and unexpected results. I'm now curious what changed-deps really does, and the man page is terse on this. I would have thought portage already does that automatically, but I see a difference. If a package's deps change, but everything is still satisfied, portage will do nothing. Does @changed-deps rebuild everything that changed anyway, regardless is portage thinks it still OK? Also, these two similar commands return different results (I have bdeps=y in DEFAULT_OPTS btw): emerge -uND --changed-deps=y world (51 packages) emerge @changed-deps (11 packages) Do you know why those commands give different results? The smaller list is a strict subset of the longer one. -- Alan McKinnon [email protected]
