Tag Archives: live

New ISO for Slackware Live PLASMA5, with Stack Clash proof kernel and Plasma 5.10.2

blueSW-64pxAfter I released KDE 5_17.06 (June edition of my Plasma 5 package set) for Slackware 14.2 and -current a few days ago, I have now also uploaded an ISO image for the Slackware Live PLASMA5 Edition based on liveslak 1.1.8.1 and Slackware-current dated “Mon Jun 26 20:36:18 UTC 2017“. It will be the only Live variant this time,

If you already use a Slackware Live PLASMA5 USB stick that you do not want to re-format, you should use the “-r” parameter to the “iso2usb.sh” script. The “-r” or refresh parameter allows you to refresh the liveslak files on your USB stick without touching your custom content. I used the script just now on my own PLASMA5 USB stick and updated that from liveslak 1.1.8 to 1.1.8.1 in no time at all.

New in the ISO

The new ISO is based on the latest slackware64-current with Linux kernel 4.9.34, gcc 7.1.0 and glibc 2.25. This is a kernel which has been patched against the Stack Clash vulnerability.

And of course it contains the latest Plasma 5 release “KDE-5_17.06” as found in my ktown repository. You will find Plasma 5.10.2 based on Qt 5.9.0, accompanied by the latest versions of Digikam, Calligra and Krita. Additionally you will find several packages from my regular repository: chromium (with flash and widevine plugins), calibre, vlc, ffmpeg, libreoffice, palemoon, qbittorrent, openjdk and more. There’s also support for Cisco AnyConnect VPN and OpenVPN connections.
The PLASMA5 ISO does not only contain the Plasma 5 Desktop Environments. As usual, it contains the LXQT and Lumina Desktop Environments as well. Both have been recompiled against Qt 5.9.

The ISO is big (4.3 GB) but there’s not much you can not do with it.

Download the ISO image

The ISO image (with MD5 checksum and GPG signature) has been uploaded to the master server (bear) and should be available on the mirror servers within the next 24 hours.

Read more about liveslak

This blog has quite some posts about the Slackware Live Edition. Check them out: http://alien.slackbook.org/blog/tag/live/ – they contain lots of insight and helpful tips.
And this was the original post (which has been edited later on so it could become a proper landing page for curious visitors): http://alien.slackbook.org/blog/slackware-live-edition/

Download liveslak sources

The liveslak project can be found in my git repository: http://bear.alienbase.nl/cgit/liveslak/ . That’s all you need to create a Slackware Live ISO from scratch. Documentation for end users and for Live OS developers is available in the Slack Docs Wiki.

Have fun! Eric

liveslak 1.1.8 and new ISO images

blueSW-64pxNot much news of late about my ‘liveslak‘ scripts. I occasionally tweak them but the modifications these days are fairly minor. I stamped a new version on the repository this week: liveslak 1.1.8 on the occasion that I wanted to generate and upload a fresh series of Slackware-current based Live ISO images. After all, liveslak is meant to be a showcase of what Slackware-current is all about, and with the recent updates to kernel, gcc, glibc and more, a refresh was more than welcome.

The Slackware Live Edition ISOs are based on liveslak 1.1.8 and Slackware-current dated “Tue May  9 23:33:37 UTC 2017“.

If you already use a Slackware Live USB stick that you do not want to re-format, you should use the “-r” parameter to the “iso2usb.sh” script. The “-r” or refresh parameter allows you to refresh the liveslak files on your USB stick without touching your custom content.

New in the ISOs

The new ISOs are based on the latest slackware-current with Linux kernel 4.9.27, gcc 7.1.0 and glibc 2.25.

The SLACKWARE variant contains exactly that: the latest slackware-current and nothing else. Ideal for testing and for checking out the status of its development.

The XFCE variant contains a stripped down Slackware with a minimalized package set but still quite functional. The small size is also accomplished by excluding all documentation and man pages, and the localizations for the languages that are not supported in the boot menu. This ISO is small enough that you can burn it to a ’80 minutes’ CDROM (700 MB).

The MATE variant (a Slackware OS with KDE 4 replaced by Mate) contains packages from the repository at http://slackware.uk/msb/current/ which is Mate 1.18.

The PLASMA5 variant (Slackware with KDE 4 replaced by Plasma 5) comes with the latest Plasma 5 release “KDE-5_17.05” as found in my ktown repository. Additionally you will find several packages from my regular repository: chromium (with flash and widevine plugins), vlc, ffmpeg, libreoffice, palemoon, qbittorrent, openjdk and more. This ISO also contains the LXQT and Lumina Desktop Environments. Both are light-weight DE’s based on Qt5 so they look nice & shiny.

The liveslak scripts support three more variants out of the box: CINNAMON, DLACKWARE and STUDIOWARE. There’s no ISO image for the Cinnamon and Dlackware variants this time. The Studioware variant is new, and you will find the download location for an ISO further down (in the “Download the ISO images” section).

What happened between liveslak 1.1.6 and 1.1.8

  • A boot-time tweak ‘nsh’ was added so that you can disable freetype’s new sub-pixel hinting if you are no fan of how the fonts look in slackware-current by default now.
  • I ensured that the XFCE ISO will again fit on a CDROM medium. Apparently the recent updates in Slackware cause packages to swell up. This reduction in ISO size required the sacrifice of quite a few packages (many X bitmap fonts, the TTF Sazanami font, the XFCE weather plugin, and GhostScript).
  • Studioware was added as a supported Live variant. From their web site: “Studioware is a project aimed at providing build scripts and packages of the best open source audio, video and photo editing software available for Slackware Linux.
  • The liveslak scripts will now download everything they need, including a local copy of the Slackware package tree if that’s missing.

Download the ISO images

This time, the ISO variants I uploaded for Slackware Live Edition are: SLACKWARE (64bit & 32bit), XFCE (64bit & 32bit), PLASMA5, MATE. These ISO images (with MD5 checksum and GPG signature) have been uploaded to the master server (bear) and should be available on the mirror servers within the next 24 hours.

There is another Slackware Live ISO, but it is not hosted by me – I simply do not have the free space for it. It’s the STUDIOWARE Live ISO and you can find it at http://studioware.org/iso.php . It’s filled with many audio, video and photography manipulation applications and you should definitely give it a try!

Read more about liveslak

This blog has quite some posts about the Slackware Live Edition. Check them out: http://alien.slackbook.org/blog/tag/live/ – they contain lots of insight and helpful tips.
And this was the original post (which has been edited later on so it could become a proper landing page for curious visitors): http://alien.slackbook.org/blog/slackware-live-edition/

Download liveslak sources

The liveslak project can be found in my git repository: http://bear.alienbase.nl/cgit/liveslak/ . That’s all you need to create a Slackware Live ISO from scratch. Documentation for end users and for Live OS developers is available in the Slack Docs Wiki.

Have fun! Eric

May updates for Plasma 5 (Slackware)

The May 2017 updates for my ‘ktown’ repository are fairly minimal, but anyway here it is: KDE 5_17.05.
This new release contains: KDE Frameworks 5.33.0, Plasma 5.9.5 and Applications 17.04.0. All of this is still built on top of Qt 5.7.1.

NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.05?

  • The ‘deps’ section has two updated packages: json-glib and sip.
  • Plasma 5.9.5 is the final bugfix release of the 5.9 series before 5.10. The oxygen theme package is now extended with Qt4 support so that KDE4 applications can blend in with the Plasma 5 applications if you use the
    Oxygen theme. See https://www.kde.org/announcements/plasma-5.9.5.php .
  • In applications-extra I updated krita and krusader, and rebuilt calligra.
  • In kde4-extragear I added a patched oxygen-gtk2 package which should fix crashes in firefox-derived browsers such as Pale Moon.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

Non-ktown packages you probably want anyway

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 because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc: will give phonon another backend to select from.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype 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.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.04. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually. Luckily, KDE 5 is mature enough that there’s almost nothing left from old KDE 4 that you would really want.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.04 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

A Plasma5 Live ISO image will follow shortly on http://bear.alienbase.nl/mirrors/slackware-live/latest/ in case you want to try it out first (check the timestamp of the ISO on the web page).

Package download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

Plasma 5 for Slackware – April edition

During the past week (ever since the source tarballs for the new Applications were made available to packagers) I have been working toward an April 2017 release of my ‘ktown’ repository: KDE 5_17.04.
This new release contains: KDE Frameworks 5.33.0, Plasma 5.9.4 and Applications 17.04.0. All of this is still built on top of Qt 5.7.1.
A Plasma5 Live ISO image will follow shortly in the usual location.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.04?

  • The ‘deps’ section has one recompiled package (because of incompatible library updates in slackware-current): dvdauthor, and five upgrades: accountsservicefrei0r-plugins, gpgme, ninja and poppler.
    There’s also one new package (but only for the Slackware -current package set): qtav as a new dependency for digikam.
  • Frameworks 5.33.0 is an enhancement release. See https://www.kde.org/announcements/kde-frameworks-5.33.0.php
  • Plasma 5.9.4 is an incremental bugfix of the 5.9 series with small fixes only. See https://www.kde.org/announcements/plasma-5.9.4.php . At first I wanted to wait for the 5.9.5 release which is around the corner but decided not to waste another couple of days. I may add the 5.9.5 later on, since that will be the final iteration for 5.9.
    I am not sticking with the long term support (LTS) releases of Plasma 5.8, as I think LTS should be targeting stable Slackware. If you want to know more about the long term support plans, go read: https://www.kde.org/announcements/plasma-5.8.0.php .
  • Applications 17.04.0 is a new major release and marks the transition of yet another pack of applications from the old kdelibs4 to KDE Frameworks (KF5). I should check what’s still based on kdelibs4 sometimes… can’t be too many left. See https://www.kde.org/announcements/announce-applications-17.04.0.php . And the release notes give more detail about the changes in packages.
    Since k3b is now part of the Applications suite, I have removed the package that I had added to ‘applications-extra’ (which was based on a git snapshot). Another package which is no longer part of my ‘ktown’ set: kajongg (it requires python3 now which is not part of Slackware). And two packages are no longer shipped because their sources are no longer part of Applications: pim-storage-service-manager and kommander.
  • In ‘applications-extra’ I added the latest releases of krita, the KDEvelop suite and of kpmcore (the partitionmanager core libraries). I rebuilt digikam against qtav.
    The newest calligra was already added last week as part of a package rebuild, caused by slackware-current library updates. Worth mentioning is that calligra, krita, ktorrent, partitionmanager, skanlite and the KDE Development Suite in ‘applications-extra’ are all KF5 based.
  • In ‘kde4-extragear’ I have added audiocd-kio4 and libkcompactdisc4 which are built from the kdelibs4-based Applications 16.08.3 sources. All of audiocd-kio4libkcddb4 and libkcompactdisc4 packages are (only) required by Slackware’s kaudiocreator.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

You may want to check out the new Plasma 5 before installing. For this purpose, I have generated a new Live ISO for the PLASMA5 variant. Look for that ISO on http://bear.alienbase.nl/mirrors/slackware-live/latest/ .

Non-ktown packages you probably want anyway

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 because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc: will give phonon another backend to select from.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype 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.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.03. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually. Luckily, KDE 5 is mature enough that there’s almost nothing left from old KDE 4 that you would really want.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.03 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

For your Slackware-current: KDE 5_17.03 with lots of goodies

Those of you who follow my repository RSS feeds have already noticed, but many people rely on the announcements I make on this blog (plus, I can give a lot more detail here).
I uploaded the packages for the March 2017 release of my ‘ktown’ repository: KDE 5_17.03. Actually, there is a lot of interesting stuff going on in this release, because I decided to do some things that were on my TODO for a long while. Read more about that below in the “NEWS” section.
What you get in this new release is: KDE Frameworks 5.32.0, Plasma 5.9.3 and Applications 16.12.3. All of this is still built on top of Qt 5.7.1.
This Plasma 5 release targets only Slackware-current for the moment, because of the PLASMA5 Live that I release in parallel. But packages for Slackware 14.2 (only 64bit) are already being compiled at the moment, so updates will be visible in my 14.2 repository in a couple of days at most.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new in KDE 5_17.03?

  • Let’s start with the ‘deps’ section this time as there are some interesting updates to be checked out. You will find two upgraded packages: phonon-vlc and qca-qt5. Also six entirely new ones to support digikam and kdenlive: lensfun, opencv, frei0r-plugins, vid.stab, dvdauthor and mlt. You may already have one or more of these installed from SBo, so make sure to upgrade to my ‘ktown‘ versions to prevent breakage in digikam and kdenlive. Notably, the SBo version of my ‘frei0r-plugins‘ package is called ‘frei0r‘.
    The two packages that required the addition of these new dependencies: ‘digikam‘ (in kde/applications-extra) and ‘kdenlive‘ (in kde/applications) were on my TODO for a long time, but they depended on ffmpeg (amongst others) and although I have been adding many dependency packages to ‘ktown’, a ffmpeg package was one bridge too far. Now that Slackware (in the -current development tree) finally has its own ‘ffmpeg’ package, I decided to go ahead and investigate what else was required to finally add digikam/kdenlive.
  • Frameworks 5.32.0 is an enhancement release. See https://www.kde.org/announcements/kde-frameworks-5.32.0.php
  • Plasma 5.9.3 is the third iteration of the 5.9 series with small fixes only. See https://www.kde.org/announcements/plasma-5.9.3.php . I am not sticking with the long term support (LTS) releases of Plasma 5.8, as I think LTS should be targeting stable Slackware. If you want to know more about the long term support plans, go read: https://www.kde.org/announcements/plasma-5.8.0.php .
    My observations about Plasma 5.9:

    • Along with Plasma 5.9 a new network configurator was added to System Settings. The NetworkManager-openvpn plugin package I added to my regular repository and which I also added to the PLASMA5 Live Edition, allows you to define new OpenVPN connections in this Plasma network configurator. Unfortunately, when choosing “import existing vpn configuration” the editor always crashes the very moment I click on a openvpn configuration file. I can however create the desired VPN configuration using the GTK based “nm-connection-editor” instead. Afterwards, this new VPN definition is visible and usable in the Plasma 5. But I really would like the Plasma editor to work too. A bug report which I opened could not be confirmed  by the developer because he can not reproduce it – apparently the cause is something in Slackware, or in my packages.
  • Applications 16.12.3 is an incremental fix-release in the 16.12 series. See https://www.kde.org/announcements/announce-applications-16.12.3.php . I was finally able to compile the ‘libkface‘ and ‘kdenlive‘ packages now that their dependencies have been fulfilled. Kdenlive is a (free and powerful) non-linear video editor and having this in Slackware’s Plasma 5 is an exciting enhancement.
  • Applications-extra contains two new packages: ‘digikam‘ and ‘krusader‘. Krusader is a KF5-based advanced twin panel (commander style) file manager with lots of data manipulation tools. I added this one on request of one of my readers. And Digikam is the well-known photo management suite for KDE. Its KF5 port needed some dependencies which I finally fulfilled so I could add it to my repository. And glad about that, too. Years ago I ranted about how the digikam developers made it impossible for packagers to fulfill the program’s dependencies on a stable platform like Slackware and at that time I made the decision to stop making packages for it out of sheer frustration at the lack of answers.
    I have also added a beta release of k3b (now finally a KF5 port) which will see its first new official release as part of Applications 17.04 next month. Lastly I upgraded the kdevelop related packages.
  • In plasma-extra I rebuilt the sddm-qt5 package, enabling the dutch translation and making sure that SDDM picks up your $LANG settings.
  • Also worth mentioning: with every release of Plasma and Applications, the Qt4 legacy becomes smaller. Only a limited amount of qt4/kdelibs4 packages remains. And KF5 ports of k3b, calligra, krita, ktorrent, partitionmanager, skanlite and the KDE Development Suite can be found in the “kde/applications-extra” subdirectory.

This upgrade should be relatively straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. For users who are running slackware-current, the most crucial part is making sure that you end up with Slackware’s packages for ‘libinput‘ and ‘libwacom‘. I had those two packages in the ‘current’ section of my repository for a while (they are still part of the ‘14.2’ section) but Slackware added them to the core OS. Failing to install the correct (i.e. Slackware) packages, may render your input devices (mouse and keyboard) inoperative in X.Org.

You may want to check out the new Plasma 5 before installing. For this purpose, I have generated a new Live ISO for the PLASMA5 variant. Look for that ISO on http://bear.alienbase.nl/mirrors/slackware-live/latest/ .

Non-ktown packages you probably want anyway

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 because they enable functionality in Plasma 5 that you would otherwise miss:

  • vlc – will give phonon another backend to select from.
  • python-twisted – required by kajongg to start & run.
  • freerdp: access RDP servers through krdc.

All of the above can be found in my regular package repository.

In order for kdenlive to reach its full potential, you might want to consider replacing Slackware’s ‘ffmpeg‘ package by my version with extended functionality: more supported codecs including AAC, MP3 and H.264 encoders.

Multilib considerations

If you install a 32bit program on a 64bit Slackware computer with multilib and that program needs legacy system tray support (think of Skype 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.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_17.02. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.

Note:

If you are using slackpkg+, have already moved to KDE 5_17.02 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric