My thoughts on Slackware, life and everything

Tag: kde (Page 27 of 28)

Package rebuilds for KDE 4.6.0

For those of you who are using my KDE 4.6.0 packages:

Lately there have been some massive changes to the software in slackware-current. New versions of boost, libexiv2, perl made it necessary to re-compile several of my own KDE 4.6.0 packages. Perhaps you already noticed that Gwenview no longer worked, or you were having issues with plasmoids.

So, check out my ktown repository packages and upgrade the following:

kdeartwork, kdebase-runtime, kdebindings, kdegraphics, kdeplasma-addons

They have the build number “2alien

Good luck, Eric

KDE 4.6.0 is here

We have explosive!

Targeted with deadly precision, we witness the emergence of a new major KDE release.

Have fun with these KDE Software Compilation 4.6.0 packages for Slackware-current (32-bit as well as 64-bit versions available). Slackware itself will stick with the 4.5.5 version, which is rock stable and well-tested.

Highlight of this version is that it no longer relies on HAL. This is the same approach as taken by the X.Org and XFCE developers. While X.Org relies purely on udev, there are a few additional requirements for KDE (and XFCE) which is why you won’t see these new versions of both Desktop Environments yet. The Slackware Team does not want to be confronted with a potential de-stabilization of the desktop at the end of a release cycle.

If you want to replace Slackware’s own KDE 4.5.5 with the new release, several stock slackware packages need to be updated. There are even some entirely new packages (grantlee, libatasmart, libssh, sg3-utils, udisks, upower) which are required in order to run this new version of KDE4.

You can find all of these packages in the “deps” directory for your architecture.

Accompanying this KDE release are updated packages for k3b, kaudiocreator, kdevplatform and kdevelop because the versions that are contained in Slackware will not work with KDE 4.6.  New companions for KDE 4.6 are kwebkitpart (which allows you to use webkit instead of khtml as the rendering engine in Konqueror), polkit-kde-kcmodules-1 and polkit-kde-agent-1. The two “polkit” packages replace the Slackware  “polkit-kde-1” package which does not work with KDE 4.6.

The kdepim & kdepim-runtime

There has been quite a bit of discussion about the development of the Personal Information Manager (PIM) software like kontact, kmail etc. The PIM developers were not able to release a stable version of their product in time for KDE 4.6, so you now have two choices. I’ll accompany those choices with a word of caution:

  • you can either keep the version 4.4.9 of kdepim and kdepim-runtime (these are already included in slackware-current), which is stable, and compatible with KDE 4.6,
  • OR you can upgrade to the new version 4.6beta4 which I have included together with my KDE 4.6.0 packages… and with “new” I mean “new“! The PIM software has been largely re-written from scratch and does not only integrate fully with the Akonadi storage framework but also looks quite different. Also, this is very much Beta software and may not be stable enough for production use.

See the README file for detailed installation instructions! They are especially important because of the Slackware packages you have to upgrade or remove.

Feedback welcome of course. I have been running all intermediate betas and release candidates and see many improvements over 4.5.x releases, but there are some quirks (application crashes) that I think should be ironed out in a .1 or .2 release before this should be added to Slackware itself.

Get your Slackware packages for KDE 4.6.0 here: http://alien.slackbook.org/ktown/4.6.0/ or on any of my mirrors (http://taper.alienbase.nl/mirrors/alien-kde/4.6.0/ or http://repo.ukdw.ac.id/alien-kde/4.6.0/). These packages are not fit for Slackware 13.1.

And rsync access is available as always:

  • rsync://alien.slackbook.org/alien-kde/
  • rsync://taper.alienbase.nl/mirrors/alien-kde/
  • rsync://repo.ukdw.ac.id/alien-kde/

Cheers, Eric

KDE maintenance: 4.4.1 is out

I wrote about it – deeply nested inside the comments section of a previous post – but it needs its own place in a separate post:

KDE SC 4.4.1 (first maintenance release for the 4.4 series ) has been made available and the Slackware packages can be found at http://alien.slackbook.org/ktown/4.4.1/

Again, I have made 32-bit as well as 64-bit packages. The “dependencies” have not changed since KDE SC 4.4.0, so there is nothing new or changed in the /deps/ directory. Read the README in the topdirectory for full installation/upgrade instructions, or look for my older http://alien.slackbook.org/blog/its-been-released-kde-sc-4-4-0/ post.

Note that you have to be running Slackware-current (not older than 02-march-2010) or lots of things will break!

Also note that this fixes some issues with  the previous KDE 4.4.0 packages – some of those had not been rebuilt on 02-march-2010 which resulted in a broken keyboard layout configurator and kopete’s Windows Live plugin.

So, the upgrade is warmly recommended if you are running my 4.4.0 packages right now!

Eric

KDE Software Compilation 4.4 RC2

The KDE team are getting closer to the 4.4 release of the KDE Software Compilation (“KDE SC” is the new name of what used to be called just “KDE“).

The second release candidate has been released today (the release was delayed for several days). For Slackware Linux I have prepared 32-bit and 64-bit packages with the accompanying SlackBuild scripts. You will find those at http.//alien.slackbook.org/ktown/4.3.95/ (Version “4.3.95” is the same as “4.4.rc2”).

As before, these packages are built for Slackware-current. You can safely install the KDE 4.4.rc2 packages if you are running a slackware-current from around 20 january 2010 or newer. Do not try to install these packages on Slackware 13.0.

Slackware64:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86_64/deps” directory.
  • The KDE 4.4.rc2 packages themselves can be found in “x86_64/kde
  • And of course, the localization packages (non-english language translations of KDE) are available in “x86_64/kdei“. For the first time, I was able to build all of the non-english language packs without errors.

Slackware:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86/deps” directory.
  • The KDE 4.4.rc2 packages themselves can be found in “x86/kde
  • If you need a language pack, you can grab one from the 64-bit package tree.

Here are the steps on how you download the packages and install them. You can have an older version of KDE installed, but that is not required. You will end up with KDE 4.4.rc2 installed on your system. Instructions are for the 64-bit packages, I think you can figure out how to change them if you want the 32-bit versions:

  1. Download everything in the directory http://alien.slackbook.org/ktown/4.3.95/x86_64/ :
    # lftp -c "open http://alien.slackbook.org/ktown/4.3.95/ ; mirror x86_64"
  2. Change into the directory “x86_64? which has just been created in your current directory:
    # cd x86_64
  3. Remove the no longer required kdelibs-experimental package if you still have that installed. It is part of KDE 4.3.x (i.e. Slackware 13.0 did not have this package). If you do not have kdelibs-experimental on your system, you will get a harmless error message that you can ignore:
    # removepkg kdelibs-experimental
  4. Install/upgrade the KDE 4.4 dependencies:
    # upgradepkg --reinstall --install-new deps/*.t?z
  5. Install/upgrade KDE4.4.rc2 packages:
  6. # upgradepkg --reinstall --install-new kde/*.t?z
  7. Install/upgrade a language package if you prefer to have the KDE interface in your local language (I used “nl” in the example command, you should substitute your own language code there):
    # upgradepkg --reinstall --install-new kdei/kde-l10n-nl-*.t?z

Of course, you should not run those commands while running KDE…!

A big project like KDE needs fast hardware in order to compile in a reasonable time, and I have only one machine (which also happens to be my desktop computer) where I can do this. I strive to have 32-bit packages available as well as 64-bit packages for the final 4.4 release of KDE SC like I did for this release candidate.

If you want to compile the packages from source like I did, that is entirely possible using the provided sources and build scripts.

Have fun, Eric

KDE 4.4 release candidate 1 packaged for Slackware

Just a quick update:

I have finished building Slackware packages for KDE 4.4 RC1 (aka version 4.3.90). Compared to the previous Beta2, several of the dependencies have been updated. And just as with Beta2, I was unable to create language packs for ca, da, es, et, it, sr due to docbook errors.

Get KDE 4.4.RC1 packages for Slackware-current (64-bit only) here: http://alien.slackbook.org/ktown/4.3.90/ … Because the sources and SlackBuild scripts are available as well, you should be able to create 32-bit packages quite easily yourself.

Have fun, Eric

« Older posts Newer posts »

© 2025 Alien Pastures

Theme by Anders NorenUp ↑