On Wed, 23 Jul 2014 09:24:44 -0400, gottl...@nyu.edu wrote: > I had mistakenly thought this would update all packages not at the > latest version (subject to package.accept_keywords, package.mask, ...).
It only updates runtime dependencies, you need --with-bdeps=y to update all dependencies. However, the default is no for a good reason, there's no need to update build time deps once the package is installed. > 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. > > As a result eix-test-obsolete finds that I have packages installed that > are no longer in the database. That shouldn't happen. If an installed package is removed for the tree, portage should either install the highest version that matches your settings or print a warning. > I could do > > emerge --update the-2-dozen-such-packages > > Is that wise? No, as it will add them to world (this behaviour of -u appears to vary depending on portage version, wind direction and sunspot activity). Use --oneshot. -- Neil Bothwick You can't teach a new mouse old clicks.
signature.asc
Description: PGP signature
