On Wed, Jul 23 2014, gottl...@nyu.edu wrote: > My normal updating procedure is > > EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --jobs --load-average=5" > emerge --update --changed-use --keep-going @world > > I had mistakenly thought this would update all packages not at the > latest version (subject to package.accept_keywords, package.mask, ...). > > I now realize that it only does this for the packages in world and then > follows the dependency tree. So if package A in world is up to date, A > depends of B, and a new version of B appears, B will not be updated.
This must be wrong since my procedure does sometimes offer to update non-world packages > As a result eix-test-obsolete finds that I have packages installed that > are no longer in the database. > > I could do > > emerge --update the-2-dozen-such-packages > > Is that wise? I would still want to know if the executing the last emerge command is wise and also would like to understand what my update world procedure is actually doing. > thanks, > allan PS Sorry for the error. New rule no email to gentoo-user before my morning shower.
