On Monday 22 September 2003 12:42, Norbert Kamenicky wrote: > Hi, > > I got this stupid answer on "emerge -Udp kde": > > [ebuild U ] kde-base/kdelibs-3.1.3-r1 [2.2.2a-r2] > [ebuild N ] kde-base/kdetoys-3.1.3 > [ebuild N ] kde-base/kdebase-3.1.3 > [ebuild N ] kde-base/kdenetwork-3.1.3 > [ebuild U ] gnome-base/gconf-1.0.8-r5 [2.2.1] > [ebuild U ] gnome-base/gnome-vfs-1.0.5-r3 [2.2.5] > [ebuild U ] gnome-base/control-center-1.4.0.5-r1 [2.2.2] > [ebuild U ] gnome-base/gnome-panel-1.4.2-r2 [2.2.2.2] > etc... > > While upgrade of kdelibs is clear, what does mean broken "upgrade" > of gnome related ebuilds ? (Even "D" sign missing !!!) > > I didn't find sufficient answer in mail archives how to find > which dependency forces this stupid downgrade (upgrade ?) ...
If the "D" sign is missing then the package will *not* be downgraded, it will be installed in a different slot. The portage idea of "slots" is for packages with different versions that can coexist on a system. For example, you can have gtk+-2.2 and gtk+-1.2 at the same time. Thus if you have gtk+-2.2 installed and you want to install gtk+-1.2 (e.g. as a dependency) it will be shown as an upgrade and *not* as downgrade. Hence portage will show an "U" without "D". If you want to know whether a package will be installed in a slot look for a "SLOT=" in the ebuild, e.g. for gnome-base/control-center: $ grep SLOT /usr/portage/gnome-base/control-center/*.ebuild /usr/portage/gnome-base/control-center/control-center-1.4.0.5-r1.ebuild:SLOT="1" /usr/portage/gnome-base/control-center/control-center-2.2.0.1-r1.ebuild:SLOT="2" /usr/portage/gnome-base/control-center/control-center-2.2.1.ebuild:SLOT="2" /usr/portage/gnome-base/control-center/control-center-2.2.2-r1.ebuild:SLOT="2" /usr/portage/gnome-base/control-center/control-center-2.2.2.ebuild:SLOT="2" /usr/portage/gnome-base/control-center/control-center-2.4.0.ebuild:SLOT="2" So gnome-1.4 is installed in SLOT="1" and gnome-2 in SLOT="2". Hope that helps, Renat -- [EMAIL PROTECTED] mailing list
