path: root/README.5_17.10
diff options
author Eric Hameleers <>2017-10-14 19:48:14 +0200
committer Eric Hameleers <>2017-10-14 19:48:14 +0200
commit36a36275c11523c1013d802adfdb5574e4c24eab (patch)
tree5e4169b7d622bba4b9f39c237303614c35579d7e /README.5_17.10
parentd99b22d3be20e93bda035b8bd5066cef25cb7da6 (diff)
Release of KDE 5_17.10 for SlackwareKDE-5_17.105_17.10
- PKGLIST updated with the list of available packages in this release (limited to slackware-current). - README updated.
Diffstat (limited to 'README.5_17.10')
1 files changed, 365 insertions, 0 deletions
diff --git a/README.5_17.10 b/README.5_17.10
new file mode 100644
index 0000000..a0a9845
--- /dev/null
+++ b/README.5_17.10
@@ -0,0 +1,365 @@
+Here is KDE 5_17.10 for Slackware, consisting of the KDE Frameworks 5.39.0,
+Plasma 5.11.0 and Applications 17.08.2 on top of Qt 5.9.2.
+Upgrading from the previous 5_17.09 is straight-forward.
+KDE-5_17.10 is meant to be installed on top of Slackware -current.
+It will *replace* any version of KDE 4 you might have installed! Plasma 5
+has mostly gotten rid of its Qt4 legacy. Applications 17.12 will no longer
+ship anything based on kdelibs4.
+What is the NEWS in this batch of updates:
+- A few updates in the deps section. Most importantly, qt5 was upgraded
+ to 5.9.2. Two packages were recompiled: ddcutil and gpgme.
+- Plasma was updated to 5.11.0, see
+ .
+ I compiled plasma5-nm against openconnect so that it picks up support for
+ it. However I did not add openconnect to the 'deps' section, you need
+ to install it separately if you need it.
+ New to Plasma 5.11 is the Vault. It needs an encryption backend (cryfs or
+ encfs) at runtime but I did not add these to the 'deps'. I might create
+ packages for those in my regular repository however.
+ Plasma 5.11 has more improvements, among others it comes with a new design
+ for systemsettings.
+- Frameworks 5.39.0 contains one new framework: qqc2-desktop-style, see
+- Applications 17.08.2 is a stability update for KDE Applications
+ 17.08 (where the following applications are finally also KF5 based: kmag,
+ kmousetool, kgoldrunner, kigo, konquest, kreversi, ksnakeduel, kspaceduel,
+ ksudoku, kubrick, lskat, and umbrello).
+ See .
+- In applications-extra I updated kpmcore, partitionmanager, krita and
+ the kdevelop suite (now finally including kdev-python).
+Further points of interest:
+- There are a couple of *runtime* dependencies that I did not add to the
+ ktown repository, but you may want to consider installing them yourself:
+ * vlc - will give phonon another backend to select from.
+ * freerdp: access RDP servers through krdc.
+ * openconnect: support for Cisco's SSL VPN.
+ All of these can be found in my regular package repository.
+- The following kde/kde4-extragear packages should be taken from slackware
+ itself if you still need them: kaudiocreator, kplayer, kwebkitpart.
+- Lots of packages in the 'deps' department are completely new to Slackware.
+ Since KDE 5 aka Plasma 5 is built on Qt5 (KDE 4 uses Qt4 as its base)
+ you'll find many Qt5 related packages. Also, in order for Qt4 and GTK based
+ applications to dock into the Plasma 5 system tray, more dependencies were
+ needed. So, apart from updates to regular Slackware packages and the
+ new telepathy support packages (see below), these are the new ones:
+ OpenAL, PyQT5, accountsservice, cfitsio, cracklib, ddcutil, dvdauthor,
+ frei0r-plugins, grantlee-qt4, hack-font-ttf, id3lib, json-glib, lensfun,
+ libappindicator, libburn, libdbusmenu-gtk, libdbusmenu-qt5, libdmtx,
+ libindicator, libinput, libpwquality, libwacom, libxkbcommon, lmdb, mlt,
+ ninja, noto-font-ttf, noto-cjk-font-ttf, opencv, polkit-qt5-1, qca-qt5,
+ qrencode, qt-gstreamer, qt5, qt5-webkit, qtav, sni-qt, vid.stab
+ and wayland.
+ As a side note, libinput and libwacom have become part of Slackware-current.
+ Technically that makes them redundant in the above listing, however I still
+ compile Plasma5 packages for Slackware 14.2 so I left them in.
+ The phonon and poppler packages were extended so that they now support
+ Qt5 as well as Qt4.
+ Note that the SBo version of 'frei0r-plugins' package is called 'frei0r'.
+ If you have that SBo package installed, remove it.
+- A completely new subset of "deps" packages, contained in their own
+ "telepathy" subdirectory, needed for KDE Telepathy:
+ libotr, libnice, farstream, libaccounts-glib, libaccounts-qt5,
+ signon, signon-plugin-oauth2, signon-ui, libsignon-glib, telegram-qt,
+ telepathy-glib, telepathy-farstream, telepathy-haze, telepathy-gabble,
+ telepathy-morse, telepathy-qt5, telepathy-logger, telepathy-logger-qt5,
+ telepathy-mission-control and telepathy-accounts-signon.
+- Telepathy for KDE packages are found in their own subdirectory kde/telepathy .
+- The kde/kde4 and kde/kde4-extragear directories contain packages that are
+ still required to support kdelibs4-based Applications.
+- Also worth mentioning: the KF5 ports of calligra, digikam, kile, krita,
+ ktorrent, partitionmanager, skanlite and the KDE Development Suite
+ can be found in kde/applications-extra .
+ Finally, kjots (previously contained in KDEPIM) and kuser (abandoned by its
+ developer) have been moved into kde/applications-extra as well.
+If you install a 32bit program on a 64bit Slackware computer with multilib
+and that program needs legacy system tray support (think of Steam for
+instance), you will have to grab the 32-bit version of Slackware's
+'libdbusmenu-qt' and my ktown-deps package 'sni-qt', and run the
+'convertpkg-compat32 -i' command on them to create 'compat32' versions
+of these packages. Then install both 'libdbusmenu-qt-compat32' and
+'sni-qt-compat32'. Those two are mandatory addons for displaying
+system tray icons of 32bit binaries in 64bit multilib Plasma5.
+Also explained in more detail below, upgrading to this KDE 5 is non-trivial.
+You will have to remove old KDE 4 packages manually. If you do not have KDE
+installed at all, you will have to *install* some of Slackware's own KDE 4
+packages manually.
+If you decide to install these packages on top of a fresh installation of
+ Slackware 14.2 or -current and have excluded all packages in the 'KDE'
+ package series during installation, you will be missing several add-on
+ packages. You can optionally install the following Slackware packages:
+ * amarok
+ * kaudiocreator
+ * kplayer
+ * kwebkitpart
+If you had installed KDE 4 as your default desktop previously, the removal
+of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'.
+An attempt to run 'startx' in a console will fail with a black screen.
+After installing Plasma 5 for the first time, you need to run 'xwmconfig'
+and select 'xinitrc.plasma' as your desktop session.
+Install pre-compiled packages:
+In order to install or upgrade KDE 5, follow these steps:
+Make sure you are not running KDE or even X ! If you are running an X session,
+log out first, and if you are in runlevel 4 (graphical login) you first have to
+go back to runlevel 3 (console) by typing "init 3".
+If you still have a KDE 4 installed, it must be removed first. No clean
+upgrade path can be provided! Do as follows:
+If you have Slackware 14.2 or -current's default KDE 4.14.3 installed:
+ # removepkg /var/log/packages/*-4.14.3-*
+ # removepkg libkscreen
+ # removepkg kscreen
+ # removepkg kactivities
+ # removepkg kde-workspace
+ # removepkg libmm-qt
+ # removepkg libnm-qt
+ # removepkg plasma-nm
+ # removepkg polkit-kde-agent-1
+ # removepkg polkit-kde-kcmodules-1
+ # removepkg kdeconnect-kde
+ # removepkg kdepim
+ # removepkg kdepimlibs
+ # removepkg kdev-python
+ # removepkg kdevelop-php
+ # removepkg kdevelop-php-docs
+ ..or instead of the above, simply '# slackpkg remove kde' and de-select
+ the packages you want to keep (amarok, etc).
+Alternatively, in case you are already using an older release of my KDE 5
+packages, you need to look up that particular release in the list right below
+(for instance: KDE 5_16.08) and then apply the actions shown for that KDE 5
+release *and* all more recent releases, i.e. work your way back up to this
+paragraph. Note that some of the old KDE package names were obsoleted along
+the way, they were split up, renamed or integrated and that is the reason
+for some of the 'removepkg' lines you'll see below.
+Here we go:
+If you have my 'ktown' set of KDE 5_17.09 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.07 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.06 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.05_02 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.05 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.04 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.03 installed:
+- Upgrade to KDE 5_17.04
+ Remove the packages that no longer exist in KDE 5_17.04:
+ * removepkg kajongg
+ * removepkg kommander
+ * removepkg pim-storage-service-manager
+If you have my 'ktown' set of KDE 5_17.02 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_17.01 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_16.12 installed:
+- Upgrade to KDE 5_17.01
+ If you are running Slackware-current, manually install or upgrade libinput
+ and libwacom to the Slackware versions.
+ Remove the packages that no longer exist in KDE 5_17.01:
+ * removepkg kactivities
+ * removepkg nepomuk
+ * removepkg nepomuk-widgets
+ * removepkg gpgmepp
+ * removepkg kdgantt2
+ * removepkg kde-baseapps kdepim kdewebdev
+If you have my 'ktown' set of KDE 5_16.11 installed:
+- Upgrade to KDE 5_16.12
+ Remove the packages that no longer exist in KDE 5_16.12:
+ * removepkg baloo
+ * removepkg baloo-widgets
+If you have my 'ktown' set of KDE 5_16.08 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_16.07 installed:
+- Upgrade to KDE 5_16.08
+ Remove the packages that no longer exist in KDE 5_16.07:
+ * removepkg kdegraphics-strigi-analyzer
+ * removepkg kdenetwork-strigi-analyzers
+ * rempovepkg kdesdk-strigi-analyzers
+ * removepkg kdepimlibs libkdeedu mplayerthumbs
+If you have my 'ktown' set of KDE 5_16.06 installed:
+- Upgrade to KDE 5_16.07
+ Remove the packages that no longer exist in KDE 5_16.07:
+ * removepkg /var/log/packages/noto-font-ttf-2015-09-29-noarch-1alien
+If you have my 'ktown' set of KDE 5_16.05 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_16.04 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_16.03 installed:
+- Upgrade to KDE 5_16.04
+ Remove the packages that no longer exist in KDE 5_16.04:
+ * removepkg kactivities-workspace
+If you have my 'ktown' set of KDE 5_16.02 installed:
+- No further actions are needed.
+If you have my 'ktown' set of KDE 5_16.01 installed:
+- No further actions are needed.
+Then proceed with installing/upgrading KDE 5 as outlined below.
+The example commands below are for Slackware -current but you can use
+these commands for Slackware 14.2 as well by replacing the /current/
+string with /14.2/ (provided there is a suitable 'ktown' release available
+for Slackware 14.2 of course):
+Instead of using the mirror host ,
+you could choose the alternative mirror
+If you use 'slackpkg' to automate your upgrades, be sure to blacklist my
+custom packages or else slackpkg will always try to replace my packages
+with the stock Slackware versions if the package names are identical.
+As an example, you can add the following lines to the file
+"/etc/slackpkg/blacklist" to prevent this unintentional downgrading to KDE4:
+ # These three lines will blacklist all SBo, alien and multilib packages:
+ [0-9]+_SBo
+ [0-9]+alien
+ [0-9]+compat32
+If on the other hand you are using the 'slackpkg+' extension for slackpkg
+then your "/etc/slackpkg/blacklist" file should *not* contain the above
+lines! The slackpkg+ extension enables the use of 3rd-party repositories
+with slackpkg and then Plasma5 package upgrades will be handled properly.
+To make it easy for you, here is a one-line command that downloads the whole
+'5' directory (excluding the sources), with 32-bit and 64-bit packages.
+ # rsync -Hav rsync:// 5/
+Or else, if you want to download packages for just one of the two supported
+architectures, you would run one of the following commands instead.
+If you want only the 64-bit packages:
+ # rsync -Hav --exclude=x86 rsync:// 5/
+If you want only the 32-bit packages:
+ # rsync -Hav --exclude=x86_64 rsync:// 5/
+Assuming you just downloaded the bits you want from the directory tree "5",
+you must now change your current directory to where you found this README
+(which is the directory called '5'). If you used one of the above "rsync"
+commands then you can simply do:
+ # cd 5
+From within this directory, you run the following commands as root:
+ On Slackware 32-bit:
+ # upgradepkg --reinstall --install-new x86/deps/*.t?z
+ # upgradepkg --reinstall --install-new x86/deps/telepathy/*.t?z
+ # upgradepkg --reinstall --install-new x86/kde/*/*.t?z
+ On Slackware 64-bit:
+ # upgradepkg --reinstall --install-new x86_64/deps/*.t?z
+ # upgradepkg --reinstall --install-new x86_64/deps/telepathy/*.t?z
+ # upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z
+ If you already have one or more non-english language packs installed:
+ On Slackware 32-bit:
+ # upgradepkg x86/kdei/*.t?z
+ On Slackware 64-bit:
+ # upgradepkg x86_64/kdei/*.t?z
+ If you want to have a non-english language pack installed but none is
+ currently installed, substitute your country code instead of the 'XX'
+ in the next command:
+ # upgradepkg --install-new x86_64/kdei/kde-l10n-XX-*.t?z
+ Note that these separate language packs contain only the localizations for
+ kdelibs4 based applications. All KDE Frameworks 5 based programs include
+ localizations in the packages themselves (meaning that you will get all
+ languages installed always).
+ Check if any ".new" configuration files have been left behind by
+ the upgradepkg commands. Compare them to their originals and decide
+ if you need to use them.
+ # find /etc/ -name "*.new"
+ A graphical (ncurses) tool for processing these "*.new" files is slackpkg:
+ # slackpkg new-config
+Then reboot your system.
+If all you want is to install the packages I created, then you can skip the
+remainder of the README which details how to (re)compile the packages from
+their sources; it is not required reading material.
+Building it all from source:
+Sources and scripts are separated from the packages in my 'ktown' repository.
+If you want the sources for KDE 5, run the following command to download them
+(downloading from a mirror will usually be much faster):
+ # rsync -Hav rsync:// 5/
+There are a lot of 'dependencies' for KDE 5 which you'll have to compile and
+install before attempting to compile KDE 5. Compiling and installing these
+dependencies on Slackware-current is as easy as:
+ # cd 5/deps
+ # ./updates.SlackBuild
+ # cd -
+ # cd 5/deps/telepathy
+ # ./telepathy.SlackBuild
+ # cd -
+Be prepared to wait a *long* time since this will compile a new Qt5 package
+among others. The finished packages will be stored in /tmp and will already
+have been installed/upgraded automatically.
+Then if you want to compile the KDE packages on your computer, run:
+ # cd 5/kde
+ # ./KDE.SlackBuild
+Wait a long time, and you will find the new packages in /tmp/kde_build .
+Note that these packages will already have been installed by KDE.SlackBuild !
+Reboot your computer and login to a Plasma session.
+ Eric Hameleers / alien at slackware dot com / 13-oct-2017