Tuesday, June 14, 2011

KDE 4 Slotting Changes

Within the next week, I’ll be changing how slotting works with KDE SC 4 packages in the kde-base category. All KDE SC 4 packages will be moved into SLOT=4, from their current slots (which match the KDE SC version). This will cause portage (or your package manager of choice) to take slightly longer on the first sync after the update, but will allow much simpler upgrades between KDE SC versions. As all versions of KDE will now be in the same slot, portage will see a new version of KDE as an upgrade instead of a new slot blocking the old, which will considerably reduce the list of blockers during the upgrade (usually, it will reduce it down to exactly the list of packages that should be blocked anyway).

The reason that we introduced this slotting was to support USE=kdeprefix, which allowed you to install multiple versions of KDE simultaneously, in /usr/kde/VERSION. As we can no longer support such installs, the ability to do so has been removed, and with it, the need to have separate slots for each KDE version.


  1. How are you dealing w/ multiple versions being pushed into the same slot?

  2. Currently, the only way to have multiple versions installed is to have USE=kdeprefix set, which has been removed from all the ebuilds (older ebuilds still have the flag, but it dies in pkg_setup). If you have more than one package installed in the same slot, then on its next autoclean run (generally, the next time you install a package) portage will remove all but the most recently installed version in each slot.

  3. I noticed the slot updates applied to a lot of my binary packages when I synced my portage tree last time. Now there's the answer why I had to wait so long before continuing with my updates.
    Now it is just left to say "Thank you!"
    Upgrading from KDE SC 4.X.Y to 4.X+1.Z was such a pain before. Now I'm looking more forward to KDE SC 4.7 to arrive.