Here it is, KDE Software Compilation 4.10.1. A few weeks ago, KDE 4.10.0 was added to Slackware-current, along with all its updated dependencies. Essentially that was the same set of packages which I had made available on my ‘ktown‘ repository earlier, Pat Volkerding simply recompiled them using the provided KDE.SlackBuild framework.
Being the first improvement release in the 4.10 series, I expect that you will have a smooth transition and less bugs than with KDE 4.10.0. If you are interested in the bugs which have been fixed, you can query the KDE bugtracker for the KDE 4.10.1 fix set.
The addition of KDE 4.10.0 to the ‘-current’ branch made me reconsider my packaging strategy. I have been compiling KDE packages on Slackware 14.0 since its release, to achieve maximal coverage (the packages could be used on -current as well as on 14.0). I feared that this time, it would cause too much confusion if I built the new KDE 4.10.1 on Slackware 14.0, because the rather large set of “deps” packages would have to be installed on Slackware 14.0 but not on Slackware-current (since ‘-current’ is already uptodate).
So, I have decided to move on and start compiling KDE packages for Slackware-current exclusively. This has always been my “ktown” strategy prior to the release of Slackware 14.0. Those of you who are running Slackware 14.0 can either stick with my KDE 4.10.0 packages or compile the new KDE 4.10.1 yourself – that is a straight-forward task, it’s just time-consuming. If there is a gap in my evening hours sometime soon, I will try to compile KDE 4.10.1 on Slackware 14.0 myself and upload them.
How to upgrade to KDE 4.10.1?
It’s really easy this time because there are no updated dependencies, and no new or abandoned KDE packages (if you are running slackware-current of course). As usual you will find all the installation/upgrade instructions that you need in the accompanying README file. That README also contains basic information for KDE recompilation using the provided SlackBuild script.
You are strongly advised to read and follow these installation/upgrade instructions!
Download locations (using a mirror is preferred:
- http://alien.slackbook.org/ktown/ (the master repository), rsync URI: rsync://alien.slackbook.org/alien/ktown/
- http://taper.alienbase.nl/mirrors/alien-kde/ (my fast mirror), rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/
- http://repo.ukdw.ac.id/alien-kde/ (willysr’s Indonesian mirror), rsync URI: rsync://repo.ukdw.ac.id/alien-kde/
Have fun! Eric
If I’m running slackware-current, /etc/slackware-version would say so? Mine says “Slackware 14.0”.
How would I make it slackware-current?
Thanks
Thanks Eric!
I was sitting here wondering what I could get into, then this popped up in my inbox. 🙂
Next, though, I have to make a call to my Dr. for an annual physical – yuck…..
Many thanks for all the time and work you’ve provided to Slackware and its community!
Since I’m still on 14.0 and have never compiled KDE before, I was wondering if you knew how much /tmp space would be required to compile 4.10.1 on a x86_64 system. Thanks again!
Thank you Eric.
mike, annual physical is important… you have no idea how many anomalies can be found and treat early if people do their annuals as they should.
Thanks, Eric!
P.S.: The link for the README in the post is wrong
Hi Eric, seeing as kde 4.10.0 is in -current, will this not be updated in time?
Pingback: KDE 4.10.1 package set
Robby,
I have no idea if KDE 4.10.1 gets added to -current, that is why I created the packages. I wanted to take a look at the KDE 4.10.1 bugfixes.
Eric
sandb0y, thanks for mentioning that. I fixed the link.
Eric
Nelson, you would need a couple of gigabytes of storage if you want to compile KDE. I never counted how much exactly. The KDE.SlackBuild script tries to save space by deleting the source tree (including intermediate binary code) for every program right after a package has been created for it.
You will end up with just a series of packages in /tmp/kde-build
Eric
Alan.
You can not see in “/etc/slackware-version” if you are running Slackware-current. The number in that file is not updated until shortly before the new stable release.
If you want to switch (upgrade) from a stable Slackware release to slackware-current, then the process is the same as when you upgrade from one stable release to another stable release, especially if you are using slackpkg to do the hard work. You just point slackpkg to a mirror containing Slackware-current packages.
Read http://docs.slackware.com/howtos:slackware_admin:systemupgrade for some good information about a system upgrade.
Ok so I’m attempting the build on Slackware64 14.0, which currently has KDE 4.10. Already had to upgrade cmake to get KDE.SlackBuild going, but during the kdebase building it stops with the following…
In file included from /tmp/kde-build/kdebase/kde-workspace-4.10.1/build/kwin/libkwineffects/../../../kwin/libkwineffects/kwinglcolorcorrection.h:24:0,
from /tmp/kde-build/kdebase/kde-workspace-4.10.1/build/kwin/libkwineffects/../../../kwin/libkwineffects/kwinglcolorcorrection_p.h:24,
from /tmp/kde-build/kdebase/kde-workspace-4.10.1/build/kwin/libkwineffects/moc_kwinglcolorcorrection_p.cpp:10,
from /tmp/kde-build/kdebase/kde-workspace-4.10.1/build/kwin/libkwineffects/kwinglutils_automoc.cpp:4:
/tmp/kde-build/kdebase/kde-workspace-4.10.1/build/kwin/libkwineffects/../../../kwin/libkwineffects/kwinglutils_funcs.h:379:60: error: ‘GLeglImageOES’ has
not been declared
make[2]: *** [kwin/libkwineffects/CMakeFiles/kwinglutils.dir/kwinglutils_automoc.o] Error 1
make[1]: *** [kwin/libkwineffects/CMakeFiles/kwinglutils.dir/all] Error 2
make: *** [all] Error 2
kdebase failed to build.
any ideas what other packages need to be updated on 14.0 to get this building smoothly?
Thanks Eric!
Yes! Fixed a opening windows from the taskbar! KDE 4.10 have this bug!
Thanks as always for providing these packages Eric! However, since Pat was so quick to update KDE SC in -current after the 4.10.0 release, I’ll hold off for a few days to see if a pleasant surprise hits -current. 🙂
Seeing as you’re now compiling KDE SC 4.10 for -current, does this mean you’ll hold onto your 4.9.5 packages for Slackware 14.0 users? It’d be awesome if you did…
@jaycee:
4.10.1 is now included in -Current as well
your prayer is heard 🙂
I knew Pat was going to do this so I have been recompiling my own KDE 4.10.1 packages for Slackware 14.
The new Slackware 14 packages are uploading now:
http://taper.alienbase.nl/mirrors/alien-kde/14.0/4.10.1/
http://alien.slackbook.org/slackware/ktown/14.0/4.10.1/
As well as the usual rsync access of course.
Next in queue: LibreOffice 4.0.1 !
Eric
@Willy
Praise Bob! 😀
@AlienBob
You’re too awesome! I now eagerly await your LibreOffice packages! Thanks so much for everything Eric! 🙂
No wonder my rsync script deleted current. I thought it was a mistake since i’m relocating the packages to another location, but then i saw this comment and it’s the right thing to do
I’ll like to say that I broke my netbook installing Pat’s packages over yours… dunno what happened; but the /etc/X11/xinit/xinitrc.kde went missing and kde didn’t load at all.
xfce, fluxbox etc loaded fine; but as I had limited time (and this is my working computer) I removed X and reinstalled everything… go figure.
Perhaps I am running slackware-current since all my slapt-get mirrors are slackware-current; however, my slackpkg OSUOSL mirror is 14.0…
@Weput
Did you mix -Stable and -Current release?
I went to use Pat’s package and Eric and they both are working fine here on all of my machines
Pingback: Links 7/3/2013: Ubuntu and Mir Criticisms, Android Big in China | Techrights
Hi 🙂
the new packages work well on slackware 14 but I cannot find the kde-config-touchpad.
is there an extra package for it?
Andre
There was never any kde-config-* program in Slackware’s KDE packages. Perhaps you are confused after using another distro?
Eric