On Tue, 2009-01-13 at 09:44 -0600, Paul Hartman wrote: > Hi, > > I normally do "emerge -uDvN @world" (or in other words "emerge > --update --deep --verbose --newuse @world"). Right now, it tells me > this: > > Total: 0 packages, Size of downloads: 0 kB > > I also --depclean on a regular basis to remove any unneeded packages. > Right now, it tells me this: > > No packages selected for removal by depclean > > Based on those two commands, I'm led to believe I have a fully updated > system. So, then, I am curious why when I do "emerge -e @world" it > tells me this: > > Total: 1432 packages (9 upgrades, 2 downgrades, 14 new, 1407 > reinstalls, 1 interactive), Size of downloads: 76,235 kB > > How is that possible? Where do those upgrades, downgrades and new > packages come from? What is missing from my traditional "-uDvN" > command that is causing me to miss some of those updates?
Well for one "emerge -e" will pull in build-time dependencies which "emerge -u" won't (unless it's necessary for an upgrade). So hypothetically let's say you have firefox in your world file, and you have the latest so "emerge -u @world" doesn't pick it up, but say you "emerge -e @world" and firefox needs "=automake-1.6.*" to build, but you don't have that version anymore because, say --depclean or something else cleared it out or you have automake-1.6.1 installed but it's no longer in portage but 1.6.3 is, then automake-1.6.3 might show up as New or Upgrade or even Downgrade (since it's slotted). -a
