On Wednesday 08 February 2006 21:14, Harm Geerts wrote:
> On Wednesday 08 February 2006 15:45, Daniel D Jones wrote:
> > I have kdebase-3.5.1-r1 installed.  Why is kdm-3.5.1 blocked?  Surely
> > kdebase is a requirement for kdm, and it makes no sense to say that
> > kdm-3.5.1 needs an earlier version of kdebase, does it?  I'm probably
> > missing some fundamental understanding of what's going on here.  Thanks
> > for any assistance.
>
> See the other replies for the monolithic ebuild explanation.

Have done so.  Thanks to all who replied.

> kdm is part of the kdebase package, the only thing you need to do to use
> kdm is set DISPLAYMANAGER in /etc/rc.conf
> # echo 'DISPLAYMANAGER="kdm"' >> /etc/rc.conf

The "which" command (as root) wasn't showing me kdm, so I assumed it wasn't 
installed.  (/usr/kde/3.5/bin isn't in the path for the root user.  I assume 
this is normal?)

I've now modified /etc/rc.conf to use kdm.  But I now have a problem.  if I 
log in through kdm, kde 3.3 runs.  However if I kill kdm, log into the 
console, and manually run "startx", kde 3.5 runs.  (I have "exec startkde" in 
my ~/.xinitrc.)  

After installing kde3.5, I piped the output of equery list kde through grep 
3.3 and piped that output through xargs and emerge --unmerged them all.  
I then did the same with a grep for 3.4.  emerge dutifully reported that it 
was removing all of the packages.  equery agrees with emerge:

[EMAIL PROTECTED]:/ # equery list kde
[ Searching for package 'kde' in all categories among: ]
 * installed packages
[I--] [  ] dev-util/kdevelop-3.2.1-r1 (0)
[I--] [  ] kde-base/kdeutils-3.5.1 (3.5)
[I--] [  ] kde-base/kdebase-pam-6 (0)
[I--] [  ] kde-base/kde-3.5.1 (3.5)
[I--] [  ] kde-base/kdebase-3.5.1-r1 (3.5)
[I--] [  ] kde-base/kdeadmin-3.5.1 (3.5)
[I--] [  ] kde-base/kdetoys-3.5.1 (3.5)
[I--] [  ] kde-base/kdegames-3.5.1 (3.5)
[I--] [  ] kde-base/kdemultimedia-3.5.1 (3.5)
[I--] [  ] kde-base/kdeartwork-3.5.1 (3.5)
[I--] [  ] kde-base/kdeedu-3.5.1 (3.5)
[I--] [  ] kde-base/kdewebdev-3.5.1 (3.5)
[I--] [  ] kde-base/kdeaddons-3.5.1 (3.5)
[I--] [  ] kde-base/kdepim-3.5.1 (3.5)
[I--] [  ] kde-base/kdenetwork-3.5.1 (3.5)
[I--] [  ] kde-base/kdegraphics-3.5.1-r2 (3.5)
[I--] [  ] kde-base/kdelibs-3.5.1-r1 (3.5)
[I--] [  ] kde-base/kde-env-3-r4 (0)

However, /usr/kde/3.3 and 3/4 are still there, and apparently fully populated.  
The HowTo I was using said that there might be a few configs left, but as 
near as I can tell, the whole subtrees are still there:

[EMAIL PROTECTED]:/usr/kde/3.3/bin # ls -l
total 41802
-rwxr-xr-x  1 root root  102896 Jan 15 15:44 amor
-rwxr-xr-x  1 root root    4488 Jan 15 15:44 appletproxy
-rwxr-xr-x  1 root root    4396 Jan 15 15:44 ark
...
-rwxr-xr-x  1 root root    8496 Jan 15 15:44 yaf-vorbis
-rwxr-xr-x  1 root root   10848 Jan 15 15:44 yaf-yuv

and the same for bin under the 3.4 directory.

Anyone have a clue why the old versions weren't removed?  Is it safe to simply 
delete them?  

And why is kdm loading 3.3 instead of 3.5?  (I've run etc-update to ensure 
that no config file updates are outstanding.)  Is this possibly a path issue?  
If 3.3 is in the path instead of or before 3.5 in the environment that kdm 
runs under, 3.3 would probably load instead of 3.5.

[EMAIL PROTECTED]:~ $ echo $PATH
/usr/kde/3.5/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:
/usr/i686-pc-linux-gnu/gcc-bin/3.3.6:
/opt/blackdown-jdk-1.4.2.03/bin:
/opt/blackdown-jdk-1.4.2.03/jre/bin:
/usr/kde/3.5/bin:/usr/qt/3/bin:
/usr/kde/3.3/bin:/usr/games/bin

(I manually wrapped the lines above for email purposes.)  

OK, just grepped etc for /kde/3.3 and found that 3.3 is added to the path  
in /etc/profile.env.  The warning in that file lead me to man env-update, 
which pointed me to the /etc/env.d directory.  There is a file in there 
called 47kdepaths-3.3.1, which is apparently the offending party.  Is it safe 
to simply delete the file?  More importantly, why is it still there after I 
unmerged kde 3.3?  And is this what is causing kdm to load 3.3?  The 3.5 
version of the kdepaths file in /etc/env.d is prefixed with 45.  I assume 
that the files are processed from the lowest to the highest, in which case 
3.5 should be in the path before 3.3, no matter which user is running.  3.5 
appears first in the line in /etc/profile.env.

Looking back over this message, I see that equery told me that  
kde-base/kde-env-3-r4 (0) was loaded.  Is this the correct version?  Is there 
a 3.5 version that's still masked or something?

OK, my head hurts now.  I think I'll just wait and see if any of the fine 
participants of this list can shed a bit of light into the dusky shadows 
where I find myself treading.



-- 
gentoo-user@gentoo.org mailing list

Reply via email to