Gentoo-Fu: Building KDE branches

Being a happy Gentoo user myself for about half a year, I thought I would share some tips from my personal experiences on this great distro. It’s nothing you cannot already google for; these are just some ideas/motives to further dig into for yourselves. Mayhaps I will write another post or two about Gentoo. If I ever decide to overcome my laziness 🙂 Take it easy with this post, it’s a bit lengthy, but to quote Blaise Pascal: “I haven’t had time to make it shorter yet“.

Gentoo being a source-based distribution allows for some very cool stuff like building from an upstream git branch. You can find ebuilds for KDE branches 4.9 and master (as of 17.08.2012), which can vastly help you with bug triaging/fixing. Bug triaging is as easy as updating your system from this branch and trying to reproduce bugs (the procedure is fully automated thanks to Portage’s Moo Powers – “emerge --moo” – and the Gentoo Developers). Bug fixing is as easy as writing a patch and applying it using Portage’s excellent patching abilities. I actually *fixed* a bug like this recently (Bug #297209), being too lazy to manually pull and compile the source code. Sure, a manual setup is way more flexible, but doesn’t come without quite some hassles.

These ebuilds are available from overlays [1] and there is a full-blown guide on how to install KDE from these ebuilds [2]. I won’t go into much detail here, these guides are more than enough; I will simply mention what the situation is like on my system. Actually I will simply quote my system updating process (it slowly builds into a ritual the more you delve into Gentoo) and more details will pop up in time:

# layman -S; emerge --sync
# emerge -uDNavbk --with-bdeps=y @world
# FEATURES="ccache" smart-live-rebuild -E -- -av1b
# emerge -ca; emerge -Pa; revdep-rebuild -- -av1b
# eclean-dist -dn; eclean-pkg; emaint -f all

So, let’s go through this and don’t forget: man pages are your friend.

# layman -S; emerge --sync

Updates the overlays and portage’s cache. Nothing fancy here. This is your “sudo apt-get update” friend, masqueraded. Or “sudo pacman -Sy”. Whatever; all distros share some core principles.

# emerge -uDNavbk --with-bdeps=y @world

Now, this is a beast of command line options. All over the net you will find references to -uDNav (I think it has almost become Gentoo’s “sudo apt-get upgrade”), but I have spiced it with some extra options. I will go shortly through these but “man emerge” is the way to go.

-u is shorthand for --upgrade. It pulls the latest versions of the packages specified – here we specified the @world set which is laid out in your world file [3]. In other words, these are your explicitly installed packages (all the other installed packages are dependencies to these).

-D is shorthand for --deep. It takes into consideration the whole dependency tree of the packages specified, not just their immediate dependencies. Without this you would only be updating the packages specified in the @world set along with their immediate dependencies.

-N is shorthand for --newuse. It takes into consideration packages that may not have new versions but whose USE flags have changed since last compilation. After meddling with USE in /etc/make.conf or /etc/portage/package.use, I always issue this update command to rebuild packages as necessary.

-a is shorthand for --ask. Always include this option (or -p/--pretend instead), otherwise Portage will move on without confirmation. You don’t want that.

-v is shorthand for --verbose. A little verbosity is always nice 🙂

-b is shorthand for --buildpkg. Just before installing a package, this option creates a binary package out of it and stores it in /usr/portage/packages/. It may hurt a bit your compilation times and your disk’s free space, but it comes in really handy if you move back and forth KDE’s branches like me. When I was testing my patch in multiple branches (4.8, 4.9, master) recently, the effort+time to switch between them was minimal. But this requires the next option:

-k is shorthand for --usepkg. Practically it instructs Portage to use binary packages created with -b, to [greatly] shorten compilation times.

–with-bdeps=y updates the build dependecies too. These are normally not included, Portage needs to be explictly told to do so, and I use it merely because I want a fully updated system (improves my Gentoo Feng-Shui).

So practically -uDNav is the de facto update command in Gentoo and -bk allows for using binary packages (which is really great: it never hurts to have some binary packages laying around, you never know when you’ll need them – especially useful when downgrading).

# FEATURES="ccache" smart-live-rebuild -E -- -av1b

This is where the fancy stuff happen. Ebuilds from the kde overlay pull the source code straight from KDE’s Git and Subversion repositories, but have a fixed version (e.g. the ebuilds from the 4.9 branch all have a version of This is not really cool because their version remains the same all the time and the update command I mentioned above won’t update these ebuilds. You either have to manually re-emerge these packages (after manually monitoring the source code repositories for commits – zero coolness points) or install a tool to monitor the remote git repositories for commits since the last time you compiled and update the packages as necessary. So, you need smart-live-rebuild (available in Gentoo’s official repos).

It will record the commit from which you built last time and in the future won’t rebuild this package unless a newer commit has occured. Extra coolness points. But it wouldn’t be that cool if it wasn’t combined with the preceding FEATURES=”ccache” (there is an official tutorial about configuring ccache for your reading pleasure [4]). I have configured it with a 5GB cache over here but I only use it for live ebuilds which need frequent re-compiling. ccache will slow down the first compilation a bit but future compilations will be blazing fast, which is the key to maintaining a fully updated installation from a KDE branch.

Command line options explained:

E is shorthand for --no-erraneous-merge. Simply don’t emerge packages for which the update has failed.

terminates the smart-live-rebuild options. Any remaining options will be directly passed on to emerge.

av1b we have gone through this. -1 stands for --oneshot and it won’t append the packages emerged to your world file [3]. Since these packages are already installed, you only wish to update them. -1 is definitely not necessary here as smart-live-rebuild explicitly includes --oneshot on its own. I include it for symmetry with the next command.

On the other hand, smart-live-rebuild is not that smart. KDE’s infrastructure often contains multiple packages in a single repository and a change to one will make smart-live-rebuild rebuild all the packages from this repository. For instance a change to ksmserver (which is a package contained in the kde-workspace Git repo) will rebuild *all* packages residing in this repo. Still, better than nothing 🙂

# emerge -ca; emerge -Pa; revdep-rebuild -- -av1b

This is my post-update command. It checks for unneeded packages and removes them as necessary. -c is shorthand for --depclean. -P on the other hand stands for --prune and is of similar use to –depclean, but to be honest, it hasn’t occured to me yet that –prune detects an unneeded package that –depclean hasn’t already detected. I include it for Feng-Shui reasons (it’s a fast operation so no big deal).

revdep-rebuild is another must-have tool for any sensible Gentoo user; it detects broken references to libraries (i.e. when updating to newer versions of libraries) and rebuilds packages as needed. Its command line options are explained above. Make a habit of running revdep-rebuild after every update command in order to avoid system breakage!

# eclean-dist -dn; eclean-pkg; emaint -f all

Lastly, my system maintainance command. It removes old dist files (a.k.a. source code tarballs used for emerging) along with old binary packages. Default behavior is to keep the files from packages whose version still exists in the Portage tree (as newer versions roll out, old versions are removed from the Portage tree). This can take a hell of a time for dist files because it checks the entire Portage tree several times! -dn greatly reduces this time by only keeping installed versions. This is great for a rebuild but no good for downgrading. But since you have created binary packages for previous versions, you don’t have to recompile in order to downgrade! So, problem effectively solved 😉

emaint checks for all kinds of problems in your installation and tries to -fix them. Nifty small utility.

[1] Gentoo Overlays: Users’ Guide

[2] Gentoo KDE Guide

[3] /var/lib/portage/world

[4] Caching Compilation

GRUB2/BURG Integration in KDE

No, you’re not having a dĂ©jĂ  vu, this is my second post about GRUB2/BURG support for KDM which shows up in PlanetKDE. I am sorry to abuse the planet for publicity, but I have seen quite a bit of confusion as to how KDE should be configured in order to interface with GRUB2/BURG and I would like to get some things straight.

What follows is a step-by-step guide describing how to configure KDE in order to automatically select a GRUB2/BURG entry other than the default when rebooting:

Shutdown Dialog

If you are a GRUB2 user skip the BURG instructions and vice versa.

Step 1. Inform GRUB2/BURG that you plan to use this feature:

GRUB2 instructions:

Open /etc/default/grub in the text editor of your preference (as root) and add the following:


In case a GRUB_DEFAULT option already exists, just set it to “saved”.

BURG instructions:

Edit /etc/default/burg instead. The variable name is the same (GRUB_DEFAULT).

Step 2. Update your GRUB2/BURG menu file:

GRUB2 instructions:

The menu configuration file must contain set default=”${saved_entry}”. You are highly discouraged to manually edit this file, so execute the following command (as root):

grub-mkconfig -o /boot/grub/grub.cfg

Please note that some distributions (i.e. Fedora, Gentoo, Mandriva, openSUSE) use a slightly different naming scheme for GRUB2. So you’d have to adjust the above to the following:

grub2-mkconfig -o /boot/grub2/grub.cfg

BURG instructions:

BURG users should execute the following command (as root):

burg-mkconfig -o /boot/burg/burg.cfg

Step 3. Inform KDE that you are using GRUB2/BURG:

GRUB2 instructions:

Select “Grub2” as your bootloader under “System Settings > Login Screen > Shutdown > Boot manager”.

BURG instructions:

For KDE >= 4.8.0:

Select “Burg” as your bootloader under “System Settings > Login Screen > Shutdown > Boot manager”.

For KDE < 4.8.0:

Select “Grub2” as your bootloader under “System Settings > Login Screen > Shutdown > Boot manager”.

Step 4. Create symlinks:

GRUB2 instructions:

This step only applies to Fedora/Gentoo/Mandriva/openSUSE (or any other distribution which uses /boot/grub2 instead of /boot/grub)! If this is not the case for you, skip it.

For KDE >= 4.8.3:

You don’t have to do anything! You may safely skip this step.

For KDE < 4.8.3:

Execute the following commands (as root):

mkdir /boot/grub
ln -s /boot/grub2/grub.cfg /boot/grub/grub.cfg
ln -s /sbin/grub2-reboot /sbin/grub-reboot

In the above commands replace /sbin/ with wherever the grub2-reboot binary is installed. You can easily determine this with “which grub2-reboot”.

BURG instructions:

For KDE >= 4.8.0:

You don’t have to do anything! You may safely skip this step.

For KDE < 4.8.0:

Execute the following commands (as root):

mkdir /boot/grub
ln -s /boot/burg/burg.cfg /boot/grub/grub.cfg
ln -s /sbin/burg-reboot /sbin/grub-reboot

Same rule as above applies here: if the burg-reboot binary is not located under /sbin/, locate it with “which burg-reboot”.

Step 5. Reboot!

That’s it, you’re done! Now either reboot or restart KDM (something like “/etc/init.d/kdm restart”) and you’re all set 😉

As a side note, GRUB2 Editor (supports BURG) automatically adjusts your configuration to the above (i.e. it automatically performs steps 1 and 2).

Feel free to link to this post in linux forums as a reference. All of the above refer to KDE >= 4.7.

Hello planet!

Not my first post on Planet KDE but let me introduce myself: I am Konstantinos Smanis (Artemis_Fowl/ksmanis on IRC), a Greek undergraduate studying electrical & computer engineering.

Primary task of mine is to make interaction with GRUB/GRUB2 as painless as possible for the average user. Occasionally I will fix issues that really bug me or implement features I miss (for KDE), plus other minor contributions.

A bit of history: my first contribution to the open-source community was QGRUBEditor, a Qt GUI to edit GRUB (Legacy) settings. It started as a pet project, mainly to learn the basics of C++ and Qt, but it turned out to be useful to quite some people so after about a year it was discontinued, only to be successfully replaced by KGRUBEditor. After reaching an acceptable stage of maturity, KGRUBEditor was also discontinued, mainly due to me not having enough time to devote to it (exams etc.).

So, after 1-2 years of inactivity, I am back! Mainly working on a KDE GUI tool (it’s a KCModule actually, integrated in System Settings) for editing GRUB2 settings. Named kcm-grub2 it’s home address is on and is also hosted in KDE Playground (edit: KDE Extragear). I also do minor patches for KDE (as you already may have noticed), but I mostly focus on kcm-grub2.

So, that’s it, I’ll keep you informed about any new cool features coming 😉

Hello planet (?) and GRUB2 Support for KDM

This is my first post on Planet KDE, but uh-oh no introductions. Some of you may already know me; the rest of you should just wait for an introductory post (I must get to write one of those sooner or later).

I don’t want to tire you, so long story short: KDM has just gained GRUB2 support. What this means is that you are now able to reboot-once in another GRUB entry without affecting your default one:

Shutdown Dialog

This patch can be found in KDE Git (commit) and should be in for 4.7. Configuration instructions can be found here. Enjoy 🙂