When I update world including dependencies (emerge -DUup world) I get 10 _new_ packages to install, this result seems a little wierd at first. The only possible way to get a new package would be if the package is slotted, like the linux kernel, right?
What I get is:
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuild N ] gnome-base/ORBit2-2.8.2
[ebuild N ] gnome-base/libbonobo-2.4.0
[ebuild N ] x11-libs/pango-1.2.5
[ebuild N ] dev-libs/atk-1.4.0
[ebuild N ] x11-libs/gtk+-2.2.4-r1
[ebuild N ] gnome-base/gconf-188.8.131.52
[ebuild N ] gnome-base/gnome-vfs-2.4.0
[ebuild N ] media-libs/speex-1.0
[ebuild N ] media-libs/xine-lib-1_rc2
[ebuild N ] sys-kernel/gentoo-sources-2.4.20-r9
I have not installed xine-lib on my computer, so it can defenatly not be caused by slotted packages. Now I would think that the reason xine-lib is now in my list is because a package I have installed earlier have changed dependencies to include xine-lib? If this is true, then that package should probably be recompiled to make use of xine-lib, however this is not done by portage, so installing xine-lib on my computer is totally pointless, unless the package that now depends on xine-lib is updated too, which would have to install xine-lib by itself anyway!
So what happens is, I get installed a lot of packages that are useless for my system untill some other package gets updated. So either portage should recompile the packages that caused these new ones to appear, or it should simply skip them, and let an update to the original packages handle the new ones.
Need more info. Reopen if you can reproduce this.
Do it without '-U'
and add 'emerge info'
Closing due to old age