KDE SC 4.4.4 available for Slackware 13.1

I asked Pat if he was planning on an early start of slackware-current now that the sources for KDE SC 4.4.4 are available. But he said, go ahead, build your own set.

So here they are, my packages (32-bit and 64-bit) for Slackware 13.1 that give you KDE SC 4.4.4!

The routine has not changed, and the README explains the simple upgrade process as always. This time, it is even easier because I did not have to update or add any dependencies. The KDE and KDEI packages are all that’s new.

There will be a source release of KDE 4.4.5 too, somewhere near the end of june, and then it’s waiting for a stable 4.5 release. I have no idea if there are going to be Slackware packages for 4.4.5 in slackware-current, but I am going to invest some time in checking out the build process for KDE SC 4.5.

Have fun! Eric

Edit (07-jun-2010):

And oh, there is an easy way to mirror my KDE packages… using rsync! The rsync URI is rsync://alien.slackbook.org/alien-kde/ and these are the commands to either download 32-bit packages (will create a local “x86” directory) or 64-bit packages (will create a local “x86_64” directory):

$ rsync -av –progress rsync://alien.slackbook.org/alien-kde/4.4.4/x86 .

$ rsync -av –progress rsync://alien.slackbook.org/alien-kde/4.4.4/x86_64 .

Note the dot at the end of the command!


22 thoughts on “KDE SC 4.4.4 available for Slackware 13.1




  1. “First, change your current directory to where you found this README”

    how do i do that? coz i’m still newbie in slackware world.
    Please enlighten me mr.bob.


  2. Thank you Eric! I’ll be installing this tonight! Thank you so much for all you do for the Slackware community!


  3. Thank you Eric! I’ll be installing this tonight! I hadn’t been much of a KDE fan till I started using it with 13.1. Thank you so much for all you do for the Slackware community!




  4. I have some questions and hope that will find their reply:

    1) Before run upgradepkg I should wget it?
    2) Will be there a problems with the version of the other software and for example later upgrade to current?

    Thank you for everything!


  5. @George:
    Yes, you need to download the packages locally before you can run the upgradepkg commands.

    If slackware-current starts moving again, I expect that there will be an addition of a newer KDE 4.x at some point. In the meantime, there is no harm in installing my KDE 4.4.4 packages on top of Slackware 13.1 or -current because those KDE packages are self-contained and no other program in Slackware depends on them.

    Eric


  6. Thanks Eric to bring us KDE SC 4.4.4, this is very nice.
    Just because I’m curious, what’s your machine for the compiling and how long does it take to compile KDE SC ?


  7. @greg:
    I have been building packages on the same old machine for years now. It is a no-name computer powered by an AMD Athlon64 3200+ with 2GB of RAM… a slug by today’s standards.
    Naturally, building KDE takes many many hours on that hardware, and then I have to compile it twice (for 32-bit and 64-bit).
    While the compilation runs, I use the “family computer” in the living room or my little netbook to relax or work.

    Eric



  8. Thanks Eric. Indeed, the kde4.4.5 has a snappier feeling. That’s the impression i had after upgrading my laptop with 4.4.5.


  9. Thanks Eric. Indeed, the kde4.4.5 has a snappier feeling. That\’s the impression i had after upgrading my laptop with 4.4.5.




  10. Pingback: Why KDE 4.4.3 doesn't work for me? :(


  11. Pingback: KDE 4.4.4 builds fine with 4.4.3 Slackbuild. - Page 2

  12. HY, iยดm from Brazil….I tried to install slackware 13.1 x64 on a dell raid controller with H700, did not recognize the discs. error: Failed initialization of WD-7000 SCSI Card / megasas: FW now in Ready state. Any idea? The Slackware 13.0 x64 RUN!!!!!!


  13. Thanks Eric for the rsync – much better than manually trolling links – but I must point out that I was reading the link on one machine and typing it manually on another, and due to the small font I read the “–progress” part of the command as “-progress” and got really strange errors that confused me for a while…
    I’ve been putting off trying the new KDE for awhile and finally made the jump. Enjoying it so far.


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.