Re: [gentoo-user] Still kde problems with monolithic->split

[Alan McKinnon]

On Sunday 05 October 2008 07:19:37 meino.cramer@×××.de wrote:
> It getting more confused:
>
> This morning I did a
>
> emerge -pvuNDt world
>
> again and it shows me nothing suspicious.
>
> But doing a
>
> emerge -pv kde
>
> still reports:
>
> Calculating dependencies... done!
> [ebuild  N    ] kde-base/kdebase-3.5.9-r3  USE="branding cups hal ldap
> opengl pam -arts -debug -ieee1394 -java -joystick -kdeenablefinal
> -kdehiddenvisibility -lm_sensors -logitech-mouse -openexr -samba
> -xcomposite -xinerama -xscreensaver" 0 kB [ebuild  N    ]
> kde-base/kdemultimedia-3.5.9  USE="alsa encode gstreamer mp3 vorbis -akode
> -arts -audiofile -debug -flac -kdeenablefinal -theora -xine -xinerama" 0 kB
> [ebuild  N    ] app-crypt/qca-1.0-r3  0 kB
> [ebuild  N    ] kde-base/kdeedu-3.5.9  USE="-arts -debug -kdeenablefinal
> -kig-scripting -solver -xinerama" 0 kB [ebuild  N    ]
> kde-base/kdetoys-3.5.9  USE="-arts -debug -kdeenablefinal
> -kdehiddenvisibility -xinerama" 0 kB [ebuild  N    ]
> kde-base/kdewebdev-3.5.9  USE="-arts -debug -doc -kdeenablefinal -tidy
> -xinerama" 0 kB [ebuild  N    ] kde-base/kdegames-3.5.9  USE="-arts -debug
> -kdeenablefinal -kdehiddenvisibility -xinerama" 0 kB [ebuild  N    ]
> kde-base/kdepim-3.5.9-r1  USE="-arts -debug -gnokii -kdeenablefinal -pda
> -xinerama" 0 kB [ebuild  N    ] kde-base/kdenetwork-3.5.9  USE="ssl -arts
> -debug -jingle -kdeenablefinal -kdehiddenvisibility -rdesktop -sametime
> -slp -wifi -xinerama" 0 kB [ebuild  N    ] kde-base/kdeartwork-3.5.9
> USE="opengl -arts -debug -kdeenablefinal -xinerama -xscreensaver" 0 kB
> [ebuild  N    ] kde-base/kdeutils-3.5.9-r1  USE="crypt -arts -debug
> -kdeenablefinal -kdehiddenvisibility (-pbbuttonsd) -snmp -xinerama
> -xscreensaver" 0 kB [ebuild  N    ] kde-base/kdeadmin-3.5.9  USE="-arts
> -debug -kdeenablefinal -kdehiddenvisibility -xinerama" 0 kB [ebuild  N    ]
> kde-base/kdegraphics-3.5.9  USE="opengl pdf -arts -debug -gphoto2 -imlib
> -kdeenablefinal -kpathsea -openexr -povray -scanner -xinerama" 0 kB [ebuild
>  N    ] kde-base/kdeaddons-3.5.9  USE="berkdb sdl -arts -debug
> -kdeenablefinal -xinerama" 0 kB [ebuild  N    ] kde-base/kde-3.5.9
> USE="-accessibility" 0 kB
> [blocks B     ] kde-base/khelpcenter:3.5 (is blocking
> kde-base/kdebase-3.5.9-r3) [blocks B     ] kde-base/kcminit:3.5 (is
> blocking kde-base/kdebase-3.5.9-r3) [blocks B     ] kde-base/kcontrol:3.5
> (is blocking kde-base/kdebase-3.5.9-r3) [blocks B     ]
> kde-base/kdesktop:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B
> ] =kde-base/kdebase-3.5* (is blocking kde-base/kdesktop-3.5.9-r1,
> kde-base/khelpcenter-3.5.9, kde-base/kdialog-3.5.9-r1,
> kde-base/kdepasswd-3.5.9, kde-base/kcontrol-3.5.9, kde-base/kicker-3.5.9,
> kde-base/kdesu-3.5.9, kde-base/kcheckpass-3.5.9, kde-base/kdm-3.5.9,
> kde-base/konqueror-3.5.9, kde-base/kcminit-3.5.9) [blocks B     ]
> kde-base/kdm:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B     ]
> kde-base/kdesu:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B     ]
> kde-base/kdialog:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B
> ] kde-base/kcheckpass:3.5 (is blocking kde-base/kdebase-3.5.9-r3) [blocks B
>     ] kde-base/konqueror:3.5 (is blocking kde-base/kdebase-3.5.9-r3)
> [blocks B     ] kde-base/kdepasswd:3.5 (is blocking
> kde-base/kdebase-3.5.9-r3) [blocks B     ] kde-base/kicker:3.5 (is blocking
> kde-base/kdebase-3.5.9-r3)


This output is correct.


> it reports packages of kde to be updated, which are not shown with
>
>
> emerge -pvuNDt world


This is also correct


> same goes for
>
> emerge -pv gnome
>
> which shows me a bunch of gnome related packages to be updated, which
> are not shown with  emerge -pvuNDt world.
> It seems the "world" of emerge is smaller as my system ?!?
>
> What is wrong here? What did I so badly wrong?

You did nothing wrong, you just have the wrong idea about what portage is 
telling you.

Step back and think about this for just a second. When you run 'emerge kde' 
you are asking portage to add new package to your system, and they will go in 
world. It will also show all new packages that will be installed due to 
DEPENDs. That's why ever line in that output starts with [ebuild  N   ] - 
they are new to your system.

When you run 'emerge -pvuND world' you are asking portage to update your 
entire system, do a deep resolve looking into DEPENDS as well, and to take 
changed/added/removed USE flags into account as well. This will not add new 
packages as you didn't tell portage to install any new packages. Kinda 
obvious really...


-- 
alan dot mckinnon at gmail dot com