Emerge -pv output for non-slotted ebuilds does let you compare easily what version number of an ebuild would get installed and what version number might already be installed. Not so for slotted stuff, as you can see in the additional information field: It is not immediately clear there's jdk 1.5 installed already when you do emerge -pv jdk I was told on irc there's "emerge -pvC <virtual>" to get information about previously filled slots -- but that can't be it, can it? Reproducible: Always com ~ # emerge -pv jdk These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] dev-java/sun-jdk-1.6.0.03 USE="-X -alsa -doc -examples -jce (-nsplugin) -odbc" 60,724 kB [ebuild NS ] virtual/jdk-1.6.0 0 kB Total: 2 packages (2 in new slots), Size of downloads: 60,724 kB com ~ # emerge -pvC jdk >>> These are the packages that would be unmerged: virtual/jdk selected: 1.5.0 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed.
no idea what "sth" means ... going to guess you actually meant "examples"
Fixed in r9488 and released in sys-apps/portage-2.2_pre5. This bug should be RESOLVED FIXED and block bug #210077.
This is supposed to be fixed in portage-2.2_pre5 or earlier.
