On Tue, Feb 27, 2018 at 12:05 PM, Ian Zimmerman <i...@very.loosely.org> wrote: > On 2018-02-27 16:44, Paul Colquhoun wrote: > >> > > Yes, I use --deep. I've run into cases many times in the past >> > > where portage was skipping updates unless I used --deep. >> > >> > You might want to avoid combining both --deep and --changed-deps. > > 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? If so, how would two runs of > emerge (each with one of these options) help? Based on my naive > hypothesis above, emerge --deep would do everything that emerge --deep > --changed-deps would. >
Yeah, I mixed up --deep and --with-bdeps=y. I would use --deep across the board - you want your runtime deps to be up to date. In my regular update script I have: ionice -c 3 nice -n 15 emerge -auDkv --changed-use --keep-going --with-bdeps=n --changed-deps --binpkg-changed-deps=y --backtrack=100 world I'll note I haven't had a particularly exciting number of package rebuilds in the last few days. --binpkg-changed-deps is probably not essential as this setting is actually the default, but since I use binary packages as much as I can (built with cron the night before) I don't want old stale packages to be used if I'm using --changed-deps, since that is just a waste of disk IO. I use --changed-deps because I don't quite trust devs to be revbumping stuff when they should. Many will argue it shouldn't be necessary, and if we were better with QA I'd agree. I use --with-bdeps=n because I really don't care that much about build-time deps, other than stuff that is going to get updated anyway like gcc. These packages don't even need to be installed for software to work correctly, and if a dev does miss an RDEPEND there is a decent chance they'll miss it in DEPEND also. Once in a blue moon I'll run into a situation where something has a bad build dependency or a build system otherwise gets broken and I'll go ahead and do a one-time update with --with-bdeps=y. I probably would leave out --changed-deps in this case unless things are still broken. Though, I do this so rarely I suspect it wouldn't make much difference as so many build-time deps are going to get updated anyway. -- Rich
