Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



KDE 4.8.2 – updated in Slackware soon (hopefully)!

The KDE team released the next update in the KDE 4.8 cycle today. As expected it is mostly on target again.

The sources were made available to packagers some days earlier and that enabled me to update my scripts and start building on time.

I am running KDE 4.8.2 myself and so far, have not found issues. If you find any, be sure to discuss them on this blog page. I have packages ready for you to download & enjoy!

As usual, my README file containsย  detailed installation/upgrade instructions. Do not fail to follow those instructions!

I have updated quite a lot of the dependencies for this release, in particular qt, libdbusmenu-qt, sg3_utils, sip, PyQt, QScintilla, shared-desktop-ontologies, raptor2, rasqal, redland, grantlee, phonon, phonon-mplayer, soprano, akonadi. I also moved libktorrent back from the “deps” directory into KDE’s “extragear” because libktorrent depends on kdelibs and therefore should be considered as being a KDE component.


And there may even better news in the near future. Pat Volkerding grabbed my build scripts to create official KDE 4.8.2 packages for Slackware-current which hopefully will be showing up in the repositories soon. This means that finally with the update from 4.5.5 to 4.8.2 (and skipping all the 4.6 and 4.7 releases) Slackware again would have a real “current” KDE environment by default. Let’s all hope Pat does not get distracted by the hordes of fans demanding attention!

Have fun! Eric


Comment from MDK
Posted: April 4, 2012 at 16:00

There are the need to update glibc? (as current is using 2.15 now and I have 2.14.1 installed on my system)

Comment from alienbob
Posted: April 4, 2012 at 16:19

Yes. as I stated, you need to be running slackware-current. And glibc-14.1 is no longer part of slackware-current.


Comment from ponce
Posted: April 4, 2012 at 17:40

thanks as usual, Eric, especially for qt-4.8.1 (and patches) ๐Ÿ™‚

Comment from Ronny Schmatzler
Posted: April 4, 2012 at 17:51

Wow that was quick. Thanks ๐Ÿ™‚

Comment from StreamThreader
Posted: April 4, 2012 at 19:38


Comment from LOE
Posted: April 4, 2012 at 20:15

Thanks a lot for your work from Russia!

PS. there are two versions of oxygen-gtk2 pakage. Is it realy necessary?

Comment from alienbob
Posted: April 4, 2012 at 20:57

LOE, you are right. I have now removed the bad package in the 32bit section, thanks for noticing it.


Comment from LukeWolf
Posted: April 5, 2012 at 00:26

Virtuoso-OSE is missing from the source directory and the package directories as well, and it complains about it missing if you try to run the alldeps.SlackBuild

Comment from Widya Walesa
Posted: April 5, 2012 at 01:12

Slackware with KDE 4.8, nice…. thanks for your works on KDE. I’m mirroring it now :-p

Comment from zbreaker
Posted: April 5, 2012 at 01:53

Many thanks again Eric for your treats to devoted slackers.
Let’s hope that Pat has a really boring spring:)

Comment from Sampa
Posted: April 5, 2012 at 02:06

Hi! On u tutorial used rsync “ok”… i get all files (32bits and 64bits) my system is 64…. i need get all files?!


Comment from escaflown
Posted: April 5, 2012 at 02:51

Thanks Eric!

Comment from Mike Langdon (mlangdn)
Posted: April 5, 2012 at 07:55

Thanks Eric – installed and running smooth for 12 hours now.

Comment from BroX
Posted: April 5, 2012 at 08:51

Thanks Eric! Sailing smoothly!

Comment from alienbob
Posted: April 5, 2012 at 08:59

Hi LukeWolf

virtuoso-ose was updated in Slackware-current, therefore there was no longer a need for me to supply the package as part of the KDE set… please upgrade to slackware-current first.
I will update the “alldeps.SlackBuild” script on the first occasion.


Comment from Stephan
Posted: April 5, 2012 at 11:24

Hi Eric,

I have installed your KDE 4.8.1 packages and I am quite happyily using them (-: !! However, I had to recompile and upgrade audacious. Another thing I would like to know is which packets I need to deactivate in slackpkg if I wanted to use it to have my slackware current installation up to date. Currently it always tries to downgrade to KDE 4.5.5.

Cheers and many thanks


Comment from willian
Posted: April 5, 2012 at 11:55

Very good, I would like to see the python 2.7 on Slackware

Comment from chrisretusn
Posted: April 5, 2012 at 13:10

Thanks, upgraded from 4.8.1. Some as silk.

Comment from alienbob
Posted: April 5, 2012 at 18:33


I have the following two lines in the file “/etc/slackpkg/blacklist”:


This keeps all my packages safe from overwriting/deleting (they all have an “alien” tag) and also all packages created by scripts hosted on (whose default tag is “SBo”).


Comment from Stephan
Posted: April 5, 2012 at 19:22

Hi Eric,

thanks for this straight forward and easy to understand solution to my little issue (-: ! I am delighted !!!!!

All the best for Easter from Berlin


Pingback from Alien Pastures ยป KDE 4.8.2 โ€“ updated in Slackware soon (hopefully)! | Linux Blog
Posted: April 6, 2012 at 02:47

[…] version updates in the “deps” section. You have to be … Continue reading here: Alien Pastures ยป KDE 4.8.2 โ€“ updated in Slackware soon (hopefully)! This entry was posted in Uncategorized and tagged bugfix, bugfix-release, kde, most-obvious, […]

Comment from Helios
Posted: April 6, 2012 at 12:29

Thanks, everything is working well.

I would like to ask if it would be possible to put the doc in the qt-4.8.2 package in a separate one, since this doc is not used by most users. I am also using “multilib”, and these giant docs appear now twice, in /usr/lib64 and /usr/lib.

Comment from Arvent
Posted: April 6, 2012 at 14:49

Thank You! Piece of great work, as usual!

Comment from Victor
Posted: April 6, 2012 at 15:30

Thanks Eric!!

Comment from escaflown
Posted: April 6, 2012 at 18:37

Hi Eric. A little bit off topic: it seems that the calibre slackbuild beome incompatible with -cuurent since the imagemagick update. I’m gettting this error: RuntimeError: Failed to load ImageMagick: cannot open shared object file: No such file or directory

Comment from alienbob
Posted: April 6, 2012 at 18:46

Hi escaflown

Unless you want to add imagemagick as static dependency into the package, you can do a simple hack which was enough to get Calibre running (no idea if it affects its functionality or stability):

( cd /usr/lib64 ; ln -s ; ln -s )

Of course, you can always recompile the Calibre package yourself on Slackware-current which will also get rid of the library version conflict.


Comment from escaflown
Posted: April 7, 2012 at 04:09

Thanks Eric! The hack did it.

Comment from dr_alex
Posted: April 7, 2012 at 13:25

Hi Eric! Sorry for newbie question and my English. Is it possible to upgrade only glibc package without kernel and then upgrade to KDE 4.8.2?

Comment from alienbob
Posted: April 7, 2012 at 14:58

Hi dr_alex

You can try upgrading only glibc but I make no guarantees. If you want KDE 4.8.2 so badly then either upgrade to slackware-current or recompile KDE 4.8.2 yourself for your version of Slackware.


Comment from jaycee
Posted: April 7, 2012 at 17:58

Hi Eric! Not that this is related to KDE, but I was wondering how you were going with creating packages for LibreOffice 3.5. Are you still plagued by the same troubles you were encountering earlier in attempting to package it? Do you think you’ll be successful in creating packages for next month’s 3.5.3 release? If you are successful, will you package it for Slackware 13.37 or Current? Your hard work in packaging for Slackware is greatly appreciated, and us Slackers eagerly anticipate your results! ๐Ÿ™‚

Comment from alienbob
Posted: April 7, 2012 at 20:06

Hi jaycee

I did not yet try LibreOffice 3.5.2, but I did not have success with the earlier sources. I gave my scipts to Willy Sudiarto but he did not find a solution either:

Currently I do not have the time to troubleshoot the build, since it takes a day between every iteration… the sources are too big.


Comment from Willy Sudiarto Raharjo
Posted: April 7, 2012 at 23:28


Still no progress on LibreOffice build. I tried to update Eric’ slackbuild script, but still no luck as well.

Your best chance is to use the one provided in SBo project for now.

Comment from jaycee
Posted: April 8, 2012 at 12:05

Hey Eric and Willy! Thanks for the update!
That’s a shame about the build failures. At least your LO 3.4.5 build is fully functional. ๐Ÿ™‚ Admittedly I don’t really need LO 3.5 – it was more out of curiosity to see if the .doc support had made any improvements at all (although it’s already good as it is). Should I encounter any .doc files that render poorly, I can indeed use the SBo build as Willy suggested to give LO 3.5 a shot. Thank you both again for such quick replies! ๐Ÿ™‚

Comment from Willy Sudiarto Raharjo
Posted: April 9, 2012 at 08:30

In most cases, docs are well supported since the era of, but it keeps getting better in LibreOffice.
You will not find any major problems when you are trying to view a simple documents with no os-spesific fonts or features.

Comment from toudi
Posted: April 12, 2012 at 14:29

i’ve got the feeling slackware 14 rc1 is coming ๐Ÿ™‚
there’s been a lot of updates in the current and now this post about kde-4.8.2 replacing 4.5.5 ๐Ÿ™‚
and in two weeks it’s a year since the previous release ๐Ÿ™‚
this is it guys a month (or more likely two) and we will have slackware 14 ๐Ÿ™‚

Eric if you can comment on that i’m sure all your followers would love to hear it ๐Ÿ™‚

Comment from Willy Sudiarto Raharjo
Posted: April 12, 2012 at 14:36

i’m really not sure about having an RC in short time, since there are still a lot of things to update and i guess the new GCC and GLIBC still have some problems with some applications out there. They might take some time to stabilize.

Having a new KDE release in -Current doesn’t mean that we are near the RC since a lot of others are still in Pat’s TODO list, such as XOrg and other libraries.

It’s most likely that next Slackware will be released this year, but only Pat can decide when willl that time be ๐Ÿ™‚

Comment from alienbob
Posted: April 12, 2012 at 19:34

Of course there is not going to be a RC soon.

Remember, Slackware is ready when it’s ready, not when a year passes.
Perhaps we will see KDE 4.8.2 next in Slackware-current, but nothing is certain yet. Even when it gets added, we will have to allow for a lot of time to find the bugs and fix them.

Comment from Kristian
Posted: April 13, 2012 at 17:24

Hi Eric,

Thanks for the updates. A non-technical question…I’d be interested to hear about how your get your kde sources-do you use git? The src tarballs only seem accessible individually which takes 000’s of mouse clicks!

Comment from alienbob
Posted: April 14, 2012 at 14:54


I do not know what you mean with “The src tarballs only seem accessible individually which takes 000โ€ฒs of mouse clicks”. You can easily download all my sources with a single command, like I explain in the README.

The official KDE SC sources are taken from the KDE ftp server, and several of the other sources which I use are checkouts from the KDE git repository at


Pingback from Latino » Blog Archive » KDE 4.8 en Slackware
Posted: April 14, 2012 at 18:21

[…] en Slackware son muy parecidas a las de la versiรณn 4.8.1 y se pueden encontrar en el blog de AlienBob y para que todo salga bien hay que leer bien las instrucciones que vienen en el archivo […]

Comment from Kristian
Posted: April 14, 2012 at 19:05

Hi Eric,

Thanks-I meant to ask about how you get the sources that you host on your rsync server, rather than how I obtain them from your server. The kde ftp site seems to only have individual tarballs for the kde source rather than an easy way of downloading them all at once.



Comment from Willy Sudiarto Raharjo
Posted: April 15, 2012 at 04:03

The package is now officially landed in -Current ๐Ÿ™‚

Comment from alienbob
Posted: April 15, 2012 at 11:10


The KDE SC sources can be downloaded with a single lftp command using or else you can use a single rsync command to get rsync://

Many of the other sources I used are taken from git repositories or from other locations at and I grab those on an individual basis. If you want to repeat that process instead of getting them from my repository, be my guest.


Pingback from calibre AlienBob’s package doesn’t run anymore on -current
Posted: June 1, 2012 at 11:17

[…] my comment posted on "April 6, 2012 at 18:46" in…oon-hopefully/ : […]

Write a comment