KDE4

From Gentoo Linux Wiki

(Redirected from HOWTO KDE4)

	K Desktop Environment
	Location: KDE4

KDE Pages

Install

KDE Desktop

Applications

Upgrading

Tips

Other

KDE/Screenshots

All KDE pages

edit

[edit] Introduction

KDE 4.1.1 is currently available only as an overlay and not in the official portage-tree. Instead the first KDE4-Realease KDE 4.0 is in portage and if you want to use it you can simply use the official KDE4-guide. However KDE 4.0 is not recommended for End-Users from the KDE Developers and you should use an overlay instead.

The newest release KDE 4.1.1 can be installed using two different Gentoo-Overlays:

The Official Gentoo-KDE-Team Overlay
The Inofficial Overlay

Each Overlay has the newest stable Version 4.1.1 and if you want to experiment a lot, then you can also try the latest development version direct from the KDE repository instead.

For now most people suggest the Inofficial Overlay for normal users, because it simply works and there are more ways to get help for that. But it is possible that the Official Overlay will be included in portage instead in the future.

[edit] 1. Overlay: Official KDE Team Overlay

As the directions for this page were outdated, please refer to the official documentation for the kde-testing overlay. Please note that after syncing the documentation will be in the tree you just synced.

The overlay is "kde-testing" in layman and can be found at git://git.overlays.gentoo.org/proj/kde.git

Installation is mostly the same as for the Unofficial Overlay.

[edit] 2. Overlay: Inofficial Overlay

This overlay is called "kdesvn-portage". It includes packages for KDE 4.1.1, KDE4-SVN and weekly SVN-sapshots. The KDE 4.1.1 should be suitable for normal users.

[edit] Layman and tools

At first you need layman to install the overlay: emerge -av layman

(For more information read the Overlay Documentation)

You also have to have git installed, if not emerge it: emerge -av dev-util/git

Now fetch and add the KDE development overlay: layman -f -a kdesvn-portage

Note: Users with older configurations will need to replace /usr/local/portage with /usr/portage/local - This is a recent change to the default layman configuration.

You can either add all your layman managed overlays to the overlay list by adding the following line to /etc/make.conf: source /usr/local/portage/layman/make.conf

Or you can add just the kdesvn-portage overlay by adding the following line to the end of /etc/make.conf: PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/portage/layman/kdesvn-portage/"

[edit] Unmasking Preparations

This overlay requires a large amount of unmasking. Fortunately there are some things in place that make it a lot easier. If you know what to do you can simply unmask your desired version of kde-meta with all the dependencies using autounmask or you read these tips how to ease it a lot:

[edit] Broken autounmask

Many people like to use autounmask to help with huge unmasks. Unfortunately it is broken in Gentoo 2008.0. Some people have reported workarounds in a Autounmask-Bugzilla-Report. But unfortunately amd64-Users can only downgrade to profile 2007.0 to make it work again: eselect profile list and then: eselect profile set # (where # is your listed profile number).

[edit] Pre-made package-keywords

It provides all the necessary files pre-made for us: package.keywords, package.unmask ...

If you already use directories for /etc/portage/package.*, you can skip straight to the unmasking section.

[edit] Converting to directories (package.* are files)

This section will show you how to switch from using a single file for each of /etc/portage/package.* to using directories. Using directories makes it easier to manage large sets of entries by just adding or deleting entire files and even autounmask will create a new file for each run.

Using the following script, the old contents of your /etc/portage/package.* files will be saved as /etc/portage/package.*/monolithic.

Copy the following file to ~/convert-profile-to-files.sh:

File: convert-profile-to-files.sh

#!/bin/bash
PROFILE_DIR="/etc/portage"

if [ ! -e ${PROFILE_DIR} ]; then
  mkdir ${PROFILE_DIR};
fi;

for PACK_DIR in package.keywords package.use package.unmask package.mask; do
  CUR_DIR="${PROFILE_DIR}/${PACK_DIR}"
  if [ ! -e ${CUR_DIR} ]; then
    mkdir ${CUR_DIR}
  fi

  if [ -e ${CUR_DIR} -a ! -d ${CUR_DIR} ]; then
    mv ${CUR_DIR} ${CUR_DIR}.moving
    mkdir ${CUR_DIR}
    mv ${CUR_DIR}.moving ${CUR_DIR}/monolithic
  fi
done

echo "Completed!"

Now run sh ~/convert-profile-to-files.sh to convert to directories.

[edit] Create package.* directories

If you've not used any of the package.* directories before, you'll need to create them:
mkdir -p /etc/portage/package.{use,mask,unmask,keywords}

[edit] Finally Unmasking

The following points are useful if you want to use the predefined Package.* files from the overlay. It creates links from /etc/portage/package.keywords to a file inside the overlay.

[edit] KDE 4.1 Only

Add the unmask entries for the overlay to your /etc/portage/package.unmask/ directory:
ln -s /usr/local/portage/layman/kdesvn-portage/Documentation/portage/package.unmask /etc/portage/package.unmask/kdesvn

Add the keywords for the overlay to your /etc/portage/package.keywords/ directory:
mkdir /etc/portage/package.keywords/kdesvn ln -s /usr/local/portage/layman/kdesvn-portage/Documentation/portage/package.keywords/*-4.1.keywords /etc/portage/package.keywords/kdesvn/

[edit] KDE 4.2 Weekly Snapshots Only

[edit] KDE 4.2 SVN Only

Add the keywords for the overlay to your /etc/portage/package.keywords/ directory:
ln -s /usr/local/portage/layman/kdesvn-portage/Documentation/portage/package.keywords /etc/portage/package.keywords/kdesvn

[edit] Installing KDE

[edit] Blockers

If you get a qt:4 blocker, to fix it run: emerge -C qt:4; emerge -av1 qt-gui

If you get a qca:0 blocker, keyword app-crypt/qca-1.0-r3 and then run emerge -av1 app-crypt/qca:0

When all the blockers are fixed... ... it is still possible to have packages that don't compile. Sometimes they need a second start to do it and sometimes you need to tweek a bit. A good start for help with this is the KDE-Portage-Thread at the Gentoo-Forums.

[edit] Portage Version Differences

[edit] Portage 2.1.x

Portage 2.1 does not feature set functionality.

To install KDE 4.1 without using the set: emerge -vat kde-meta:4.1

To install KDE 4.2 without using the set: emerge -vat kde-meta:4.2

To install all of KDE SVN without using the set: emerge -vat kde-meta:kde-svn

[edit] Portage 2.2

With Portage 2.2 you have the option of using sets.

To install KDE 4.1 using the set: emerge -vat @kde-4.1

To install KDE 4.2 using the set: emerge -vat @kde-4.2

To install all of KDE SVN using the set: emerge -vat @kde-svn

You can, of course, also install individual packages as desired using the normal syntax.

If you find any required packages which are not unmasked by the package.* files, please report them to the overlay maintainers (either via the website or the irc channel.

[edit] Installation Tuning

There are some known problems with the NVIDIA or ATI graphic drivers that cause KDE4 to have very bad performance. There are two Howtos in KDE-techbase that have workarounds or improvements for these Issues:

KDE4-NVIDIA - Specialized on NVIDIA
GPU Performance - Detailled help for ATI and NVIDIA

I recommend reading both.

[edit] Links

Retrieved from "http://gentoo-wiki.com/KDE4"

Category: KDE