public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] X86 stable emerged a bunch of KDE 4 things. How to use them?
Date: Mon, 26 Oct 2009 10:00:19 +0100	[thread overview]
Message-ID: <cba58f63cafb47a90c6f2a6bacbac8c5@localhost> (raw)
In-Reply-To: <9acccfe50910251356u3f9bce50scba3b53bcc30c72b@mail.gmail.com>

On Sun, 25 Oct 2009 13:56:24 -0700, "Kevin O'Gorman" <kogorman@gmail.com>
wrote:
> Having just emerged what looked like a couple of hundred things, many of
> them KDE-4 related, I'm surprised that on reboot I'm still running KDE
3.5.
> Moreover, there's only /usr/kde/3.5, no 4*.  The only change I noticed
was
> in the background of the login dialog.

You will not see an /usr/kde/4.x unless you have USE=kdeprefix. Since 4.x,
kde by default is installed on your regular system prefix, instead of
creating his own. So your kde binaries will usually live in /usr/bin, and
each component will go to the right place just like for any other package.

> Should I just wait, or is there something I should be doing?

I have no experience mixing branches of kde. As long as you have the 4.x
version of kdebase-startkde you should have a way to start kde4, how to do
it will depend no how do you start X. You seem to use kdm, I can't really
help with that because I don't use a DM. If you use startx from command
line it's just a matter of using the correct binary on your ~/.xinitrc, in
this case /usr/bin/startkde if I am not mistaken.
-- 
Jesús Guerrero



      parent reply	other threads:[~2009-10-26  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 20:56 [gentoo-user] X86 stable emerged a bunch of KDE 4 things. How to use them? Kevin O'Gorman
2009-10-25 21:16 ` Neil Bothwick
2009-10-25 22:18   ` Mick
2009-10-26  9:00 ` Jesús Guerrero [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cba58f63cafb47a90c6f2a6bacbac8c5@localhost \
    --to=i92guboj@terra.es \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox