One of my previous posts discussed “ABI breakage” and how that affects software to the point where it breaks and you need to recompile stuff to un-break it. Well… last week was most likely another, bigger, surprise to many of you. The Slackware-current ChangeLog.txt update of “Thu Apr 19 01:04:06 UTC 2018” started with:
Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the longest ChangeLog entry in project history). There were two primary motivations for rebuilding everything in the main tree. The first was to switch to the new C++ ABI. The second was to get rid of all the .la files in the LD_LIBRARY_PATH.
That was fun, seeing 1365 lines of ChangeLog and realizing how long the upgrade would take!
But in the end, this was a painless migration. WIth a simple “slackpkg update ; slackpkg upgrade slackpkg” to upgrade the slackpkg package itself. Don’t forget to check the new /etc/slackpkg/mirrors file to see if your mirror is still configured there! Followed by “slackpkg update ; slackpkg install-new ; slackpkg upgrade aaa_elflibs ; slackpkg upgrade-all” and a lot of patience. That’s about all there was to it and after a reboot the Slackware-current system would run as well as ever. A big accomplishment and hats off to Patrick Volkerding who used the past months to (mostly under the radar) update all the SlackBuild scripts and write wrappers to enable him to recompile all of Slackware from scratch, while gaining a lot on the efficiency and time management front. Kudos!
Ah well, a painless migration you heard me say…
Unless you have a ton of 3rd party software bolted onto your Slackware – like my Plasma5… because that came out pretty much broken. On the Slackware forum as well as here on the blog I already advised to hold off with upgrading for a day or so to give me the opportunity to at least recompile Plasma5.
And it so happened that the KDE developers already had all-new source code tarballs waiting for us. I compiled that on the freshly rebuilt Slackware-current and yesterday evening I uploaded my new set of Plasma5 packages to the ‘ktown‘ repository.
The KDE-5_18.04 release of ‘ktown‘ for Slackware-current offers the latest KDE Frameworks (5.45.0), Plasma (5.12.4) and Applications (18.04.0). The Qt5 was upgraded to 5.9.5. Read the README file for more details and for installation/upgrade instructions. Enjoy the latest Plasma 5 desktop environment.
So, what’s new?
- I had to deal with a couple of packages that were broken after the massive upgrade in Slackware, so I took the opportunity to upgrade gpgme, mlt, poppler and qt5 to a newer version; and I added QScintilla to extend the package (already available in Slackware) with support for Qt5.
- In plasma-extra the kdeconnect-framework package was updated.
- Applications 18.04.0 is the start of a new round of improvements. Two new packages are available starting with 18.04: kamoso which is a webcam recorder, and a backup program kbackup. The instant messenger client Kopete was ported to KF5 and is contained in the source distribution, but I was unable to compile it. Perhaps more luck next month.
Finally, the hex editor okteta moved to the ‘applications-extra’ section because its developer no longer wants to be tied to Application release windows.
- In applications-extra I have upgraded the kdiagram and krita packages.
If you want to read more about the history of Plasma5 development for Slackware, with lots more detail, check out my older blog posts. If you think a git log is easier to read, check out my ktown git repository instead 🙂
If you are using slackpkg with the slackpkg+ extension, don’t forget to run “slackpkg install ktown” to get any new packages installed, because “slackpkg install-new” will not catch new packages in 3rd-party repositories like ‘ktown’.
I hope to get a new PLASMA5 variant of the Slackware Live ISO image out soon, containing all this new stuff! This depends on my ability to recompile LibreOffice 6.0.3 for 64bit. I ran into a bit of a snag there with gpgme-related compilation errors I have as of yet not been able to fix. Also, VLC3 needs a rebuild since that broke too… and I have not been able to find the time to address that.
Enjoy the new batch!