Installing kde from svn to gentoo

I am a user of kde4 from the first versions that appeared in portage. And here it is ripe for the assembly of kde from svn, so that, as they say, to try svezhachka.

First of all, to build kde, we need to install a new portage 2.2. Now it is disguised to more actively test the current version of portage, but, unfortunately, only versions with support for new EAPI support package sets. Therefore, we make the following change to /etc/portage/package.unmask:

# echo ">=sys-apps/portage-2.2_rc18" >> /etc/portage/package.unmask
# emerge portage

This will allow us to use sets of packages and use directories instead of package. * Files. Accordingly, the next step is to add the kde-crazy overlay. The utility that Gentoo manages overlay laymans.
')
# USE="git subversion" emerge app-portage/layman

The included git and subversion USE flags will allow us to work with overlays based on git and svn, respectively. After the installation of layman is completed, we add the kde-crazy overlay (unfortunately, I did not find the overlay official site - so I can’t give the link).

# layman -a kde-crazy

After adding the overlay, emerge will swear at the metadata - we do not pay attention, it will not affect our task. We try to install kde-live with a swoop:

# emerge -av @kde-live

You can pay attention to the fact that instead of the standard meta-packages was used set @ kde-live. A set is simply a listing of the required packages with the required flags. Located in the portage tree in the sets directory. But back to our task. emerge scolds disguised packages.

As quickly as possible, you can defeat this problem by writing a dirty hack script that will put all ebuilds in the overlay in unmask:

#!/bin/bash

for name in `ls`; do
for name2 in `ls $name`; do
echo -n $name
echo -n /
echo "$name2 **"
done
done

We use the script as follows - put it in / usr / local / portage / layman / kde-crazy and run:

# ./script | grep -v sets | grep -v Documentation | grep -v eclass | grep -v profiles | grep -v script > /etc/portage/package.keywords/kde-live/kdefull-live

Naturally, the kde-live directory in package.keywords should exist at this point. The rest of the packages that are unmasked by version are easier to bring here (/etc/portage/package.unmask/kdefull-live)

>=app-office/akonadi-server-1.1
>=kde-base/system-config-printer-kde-9999
>=kde-base/printer-applet-9999
>=app-admin/system-config-printer-0.7.27
>=dev-python/pycups-1.9.12

Repeat build attempt with emerge -av @ kde-live
All problems that occur during assembly, most often solved when searching on the Internet. I could not collect from svn only the last package of the set - kmail-live.