Gentoo KDE 4.0 Guide
Content: 1. Installation 2. Changes from KDE 3.5 3. FAQ
1. Installation

Removing any pre-release ebuilds

If you used the genkdesvn overlay, it's advisable that you remove the KDE pre-releases from your system before upgrading. For most users this should be as easy as running layman -d kde. Also, if you modified any of the KDE related files in /etc/env.d/ you'll have to manually remove those.

Enabling the necessary USE flags

KDE 4.0 requires x11-libs/qt:4 built with a set of minimal USE flags. Add the following line to your /etc/portage/package.use.

Code Listing 1.1: Setting the necessary USE flags for x11-libs/qt:4

x11-libs/qt:4 accessibility dbus gif jpeg png qt3support ssl zlib

If you have the opengl USE flag set for KDE ebuilds, you'll have to set the opengl USE flag for x11-libs/qt:4 too.

Note: KDE 4.0.0 hasn't been tested with the Qt-4.4.0 technical preview, and at the moment of writing the KDE 4.0.0 ebuilds do NOT work with this version of Qt.

Unmasking and keywording

KDE 4.0.0 is currently hard-masked, so you will have to unmask it first before you can emerge it. Users with ACCEPT_KEYWORDS="~x86" or ACCEPT_KEYWORDS="~amd64" do not need to perform any other steps. Any other users will need to place the packages in package.keywords.
/etc/portage/package.unmask/ and /etc/portage/package.keywords/ can be directories, so you can save the following examples in those directories, to unmask and keyword KDE 4.0.0.

Example package.unmask

Example package.keywords

Installing

You can now run either of the following emerge commands, to install KDE. The first will give you all of KDE 4.0.0, built from split ebuilds.

The second will give you a minimal KDE 4.0.0 desktop, as a basis to add only the programs you like.

The third command will build all of KDE, built from monolithic packages.

Code Listing 1.2: Installing KDE 4.0.0

emerge -avD kde-base/kde-meta:kde-4
emerge -avD kde-base/kdebase-startkde:kde-4
emerge -avD kde-base/kde:kde-4

To read more about the difference between split and monolithic ebuilds, see The KDE Split Ebuilds HOWTO.

2. Changes from KDE 3.5

KDE 4 represents a dramatic change in the desktop architecture to KDE 3. One such change is the migration from autotools to cmake. This means that you will now have a percentage progress during the compilation of KDE.

The startkde script

It is not recommended to let KDE 3.5 and KDE 4.0 share the same configuration files. To prevent that the startkde scripts rewrite the ~/.kde symlink while KDE starts. This means that when you're in a KDE 4.0 session your configuration from KDE 3.5 will be unavailable and vice versa.

Because of this, you should not run two different KDE versions as the same user, at the same time. (Logging in to KDE 4.0, while KDE 3.5 is still running in the background, under the same user.)

Selecting the login manager

By default the highest version of kde-base/kdm you have installed will start on login. To configure this, open /etc/conf.d/xdm in your favorite text editor and change the DISPLAYMANAGER variable to kdm-3.5 or kdm-4.0. You can find possible versions for kdm by running ls /usr/kde/ in a shell.

Code Listing 2.1: Add the following to /etc/conf.d/xdm

DISPLAYMANAGER=kdm-3.5

3. FAQ

Q: Can I install KDE 4.0 and KDE 3.5 at the same time?

A: Yes, both versions are slotted, and can be installed at the same time. Both versions of KDE use a different KDEHOME, so you can try KDE 4.0 as the same user, without overwriting your KDE 3.5 settings.

Q: You said I could install KDE 3.5 and KDE 4.0, but they block each other!

A: You will need to install the latest revision (not version) of kde-base/kdebase (if you use monolithic ebuilds) or kde-base/kdebase-startkde (if you use split ebuilds). These versions include patches to allow multiple versions of KDE to coexist.

Note: These revisions haven't been stabilized yet, so if you use stable, you'll have to keyword those revisions.

Q: Why is KDE 4.0.0 hard-masked?

A: KDE 4.0.0 is very much a technology release. It was not intended to be a complete replacement for the KDE 3 series, yet. Many features are missing and many bugs will be found. When KDE 4.x is at the stage that it offers a true upgrade path for users, it will leave the hard-masked status.

Q: Why is KDE 4.0.0 masked by EAPI?

The KDE 4.0.0 ebuilds use slot dependencies, such as kde-base/kdebase-startkde:kde-4, in the dependency syntax. You need a version of portage that understands these. If you get this mask message, you should simply update portage to a sufficiently new version.

Code Listing 3.1: Updating to a version of portage that supports EAPI=1

# emerge --oneshot >=sys-apps/portage-2.1.3.12

Q: Where is KDE-PIM in KDE 4?

KDE-PIM wasn't released with KDE 4.0.0, so unfortunately you won't find it in the tree for a while. You can of course use the 3.5 versions of kmail, akregator and their friends, together with KDE 4.0.0.

Q: I tried KDE4 and realized I don't want it anymore, what should I do to get rid of it?

A: Remove KDE 4 from your package.keywords and package.unmask, then uninstall the packages you installed. Remember to update your DISPLAYMANAGER if you changed it to kde-4.0 earlier.

Q: Does this mean KDE 3.5 will be gone soon?

A: Not at all! KDE 3.5 is very stable, and still gets minor bugfixes from upstream. While KDE 3.5 won't see new features anymore, we do plan on maintaining it for a long time.

P.S. Сам не пробовал. Запостил сюда так как права создавать новые новости у меня нету. Источник: http://www.gentoo.org/proj/en/desktop/kde/kde4.xml