Here's the best way I can explain the problem I'm seeing: eric@xion eric $ emerge -p kdelibs These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] kde-base/kdelibs-3.2.2-r1 [3.2.2] eric@xion eric $ emerge -p world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] x11-themes/redhat-artwork-0.96 [0.95] [ebuild U ] sys-apps/baselayout-1.9.4 [1.9.1] [ebuild U ] media-sound/alsa-tools-1.0.5 [1.0.4] [ebuild U ] sys-devel/automake-1.8.5 [1.8.3] [ebuild U ] sys-apps/shadow-4.0.4.1-r2 [4.0.4.1-r1] [ebuild U ] media-sound/mpd-0.10.4 [0.10.3] [ebuild U ] sys-apps/coreutils-5.2.1 [5.2.0-r2] [ebuild U ] sys-devel/autoconf-2.59-r4 [2.59-r3] $ emerge --version Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo-r1) Not really sure what other information I can provide. Thanks. In the event of this being a "feature" it really should explain why somewhere. Reproducible: Always Steps to Reproduce: I'm not really sure how reproducable this is. Can anyone else confirm or deny?
Unless you emerge kdelibs explicitly previously, updating wont include it unless you specify the --deep option. This is preferred default behaviour as it is possible to break packages when upgrading the libs that they were compiled against.
Well it seems to me like it might be nice if there was some form of notification, especially since this update seems to fix a security hole. Also, emerge -p --deep world does not list this package. Thanks.
