Tag Archives: qt

KDE SC 4.10.0 released

Right on time, here is KDE Software Compilation 4.10.0. We left behind the 4.9 series but since this is a “zero release” I will keep my 4.9.5 packages around for a while. With this 4.10 series, one of the most interesting new features for end-users is the enhanced scripting possibilities for Plasma Workspaces (using QML, the Qt Markup Language and QtQuick) and the KWin window manager using external scripts. A new print manager has been added as well.

I have had packages ready for a few days already, and that allowed for limited testing by the people I trust. No strange bugs surfaced, if there are any left I hope you will uncover them 🙂

Remember: my ktown packages for KDE are meant to be used on Slackware-current, but I built this set of packages on Slackware 14.0. It allows these KDE 4.10.0 packages to work on Slackware 14 as well as -current.

How to upgrade to KDE 4.10.0? Whether you are upgrading from the stock KDE 4.8.5 of Slackware 14.0/current, or if you are upgrading from my previous 4.9.5 packages, you will find all the installation/upgrade instructions that you need in the accompanying README file.

You are strongly advised to read and follow these instructions!

Highlights for the new set of Slackware packages:

  • You will find nine updated dependencies compared to Slackware’s own KDE 4.8.5:  PyQt, akonadi, attica,phonon-gstreamer, qt, shared-desktop-ontologies, sip, soprano, virtuoso-ose. Several of those were updated after my previous 4.9.5 packages. I added a new one as well: qjson.
  • Some of the “extragear” of the KDE in Slackware 14/current has been updated: with new versions of calligra (accompanying the KDE 4.10.0 release), kdevelop, kdevplatform, oxygen-gtk2, skanlite (already updated for my previous package sets).
  • The “extragear” section also introduces new packages (compared to the stable Slackware): oxygen-gtk3 – which should give any software which uses the GTK+3 widget set a nice integrated look and feel when you run it in KDE; and kio-mtp which is required in order to access and manage files on devices running Android 4.0 and later. Starting with the KDE 4.10.0 release, I also added libkscreen and kscreen – this is a new screen management software which plugs into the System Settings of KDE’s Plasma Workspace. It tries to make multilple-screen management as easy as possible
  • Compared to KDE 4.8.5, but also compared to KDE 4.9.x, there were some package removals:
    • kdegames has been split up into several smaller individual packages, starting with 4.10.x
    • kdemultimedia had been split up into several smaller individual packages already, starting with 4.9.x.
    • ksecrets has been removed completely since the 4.9.x series.
    • printer-applet has been replaced by print-manager since the 4.10.0 series.

Download locations (using a mirror is preferred:

Have fun! Eric

Last maintenance release in KDE 4.9 series

The KDE developers are already well underway to a 4.10 release, having published the second Beta yesterday. But as I stated before, I will stick with the 4.9 series until at least there is a stable release of 4.10. Today marks the final update in the 4.9 series. With the publication of KDE Software Compilation 4.9.4 we are at the end of the maintenance cycle. Check out the release notes if you want to know all about what happened in the past month.

I think that 4.9.4 is a perfect companion for people running Slackware 14 or current.

My Ktown packages for KDE are specifically targeting Slackware-current, since that is what they are built on. At the moment, the development of -current has not deviated much, so that the KDE 4.9.4 packages will work well on Slackware 14 as well. That is why you will find the packages in a “14.0” directory.

Whether you are upgrading from the stock KDE of Slackware, or if you are upgrading from my previous 4.9.3 packages, you will find proper installation/upgrade instructions in the accompanying README and you are strongly advised to read and follow them.

Highlights for the new set of Slackware packages:

  • You will find five updated dependencies compared to Slackware’s own KDE 4.8.5: akonadi, qt, shared-desktop-ontologies, soprano, virtuoso-ose.
  • Since qt-4.8.4 was released a few days ago, I decided to add this version to the package set. I would have had to rebuild qt anyway in order to apply fixes for crash bugs, but 4.8.4 should be better even..
  • I had upgraded some of the “extragear” of KDE in my 4.9.3 package set and they are kept for 4.9.4: you will find new versions of kdevelop and kdevplatform, as well as oxygen-gtk2.
  • I had added a new package oxygen-gtk3 to my 4.9.3 set which is also carried to this 4.9.4 set. The package should give any software which uses the GTK+3 widget set a nice integrated look and feel when you run it in KDE.
  • And to conclude, I have added an entirely new package to this KDE 4.9.4 set, “kio-mtp” which is required in order to access and manage files on devices running Android 4.0 and later. I have not tested this, and am hearing mixed reports about its usefulness. Let me know if you use this!
  • Compared to KDE 4.8.5, there were two package removals:
    • kdemultimedia has been split up into several smaller individual packages.
    • ksecrets has been removed completely in the 4.9.x series.

Download locations (using a mirror is preferred, both my own taper and Willy’s server are fully synchronized):

 

Have fun! Eric

 

KDE 4.8.0 arrives

The release schedule could have told you in advance – here we have the first installment in the KDE 4.8 series!

The Slackware KDE 4.8.0 packages are ready for your enjoyment..

A good primer on the how and why of the modularization of KDE, resulting in an abundance of smaller packages compared to the big meta packages of Slackware 13.37, please read my earlier post about KDE 4.7.0.

My packages have been compiled on Slackware-current. There has been an incompatible update to slackware-current recently (the glibc package). If you consider using KDE 4.8.0 on one of Slackware’s earlier (stable) releases, then you have no other option than to compile packages yourself. I have written down the guidelines in another blog post..

Read the accompanying README file for installation and upgrade instructions!

Some of the highlights of these KDE packages:

  • Being the first release in the KDE 4.8 series means, there will probably be some bugs to iron out. But, I really can not find anything wrong with this point zero release. It sports a new default background “Ariya” to replace “Horos” of the 4.6 and 4.7 releases. It’s nothing but straight-line geometry, giving the desktop a professional look. The desktop feels fast and snappy, partly thanks to the upgraded Qt 4.8.0 which I added as well, but also thanks to the improvements made to kwin, KDE’s window manager. Enabling the “blur” effect should no longer slow down your desktop.
  • There are a lot of updated dependencies compared to Slackware’s own KDE 4.5.5: PyQt, QScintilla, akonadi, attica, clucene, ebook-tools, hunspell, libdbusmenu-qt, libvncserver, phonon, polkit-qt-1, qt, raptor2, rascal, redland, shared-desktop-ontologies, sip, soprano, strigi, system-config-printer and virtuoso-ose. I really hope Slackware will catch up some day, as it is no fun to maintain so many packages outside of the main Slackware tree.
  • In comparison with my previous KDE 4.7.4 the number of updated dependencies is still rather big because I wanted to offer the best experience: akonadi, attica, hunspell, libatasmart, libvncserver, phonon, phonon-xine, polkit-qt-1, qt, strigi, udisks, and upower have all been brought to their most recent versions. Note that libktorrent is now located in “deps” instead of “kde” directory because it has become a dependency for more than just ktorrent.
  • KDE dpendencies that are not part of Slackware 13.37 at all (yet): grantlee, herqq, libatasmart, libbluedevil, libssh, phonon-gstreamer, phonon-xine, sg3_utils, udisks and upower. Note that I added phonon-gstreamer and phonon-xine only after I had already released KDE 4.7.0 packages because people reported that they no longer had sound. These two packages solve that issue.

Also worth mentioning is some stuff which is not completely new, since I added these to previous releases of KDE 4.7 already (but if you are new to KDE 4.8 this will certainly interest you):

  • You will find some additional useful new applications, which are not part of the KDE core set. They are new, compared to Slackware’s own version of KDE. I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the BlueZ libraries already present in Slackware. And with KDE 4.7.0, I included kplayer, a KDE front-end to MPlayer. With KDE 4.7.2, I added Quanta Plus, which disappeared from KDE4 because that migrated from Qt3 to Qt4. It is now being worked on again, but no longer as a standalone application – instead it is available as a plugin to the Kdevelop Platform. And with KDE 4.7.3, I added a native WICD applet for KDE, called “wicd-kde“. It can replace the GTK based “wicd-client” which is part of the wicd package.
  • I also added oxygen-gtk2 (renamed from “oxygen-gtk” now that there is also a version supporting GTK3). It is not really an application, but a theme engine. It (optionally) makes GTK2 applications visually blend in with KDE’s own Oxygen theme. There is a README in its documentation directory which explains how to enable it.
  • Since KDE 4.7.2, I include a “test” directory. This directory contains NetworkManager, plus some other dependencies, that allows me to create a KDE package for “networkmanagement“. Networkmanagement is an applet plus a kcontrol (i.e. a plugin for KDE’s systemsettings). Use the packages in this “test” directory if you want to switch from WICD to NetworkManager as your basic network management service. The applet plus kcontrol make it quite easy to configure your network in KDE (wired, wireless, vpn, dsl and mobile broadband). No new Gnome libraries had to be added for this (NM itself plus its supporting tools have no dependency on the rest of Gnome). I have added NM installation/configuration instructions to the README. Note that I moved from NM 0.8 (which I had in KDE 4.7) to the newer NM 0.9 because that is what KDE currently supports best.

The KDE 4.8.0 packages for Slackware-current are available for download from my “ktown” repository and several mirrors (taper will probably be in sync when I post this, the other mirrors will have to catch up):

Have fun! Eric

KDE SC 4.4.5 for Slackware 13.1

Well folks, we had short discussion about who would do the first build of KDE SC 4.4.5 for Slackware. But since Pat is on other duties at the moment, I took the opportunity to release a set of packages for the recently released KDE Software Compilation 4.4.5. ( KDE people, there is a lack of Slackware team members at Akademy this year… let us know in advance next year and I will make an effort to be there! )

Anyway, you can find the packages for Slackware 13.1 (32-bit as well as 64-bit) in my ktown repository. This time, there are several non-KDE packages which received an update, Qt being the largest of those. Qt 4.6.3 is supposed to fix a few bugs that affect KDE’s plasma desktop. You will find the updated dependencies in the “deps” directory.

There is a README which explains the straight-forward  installation/upgrade steps.

I expect that slackware-current will follow suit (soon-ish… perhaps in one of two weeks?) with an official set of packages from Pat, and with the same updates to non-KDE packages which should make the upgrade from my packages to slackware-current real easy.

I invite you to check out my KDE packages  before that time (your feedback gives us the chance to iron out any wrinkles before KDE 4.4.5 enters slackware-current).

In case you had not noticed earlier, there are koffice-2.2.0 packages too, inside the KDE 4.4.5 directory tree. I had built them after I uploaded KDE 4.4.4 but they never got a real good announcement. By the way, if you subscribe to my ktown RSS feed, you will not miss out on updates like that!

Now that koffice-2.2.1 is about to be released, I hope that Pat uses that for the next Slackware update.

Have fun!

Eric

Fiddling with the KDE 4.5 beta

Although it seems (by looking at the changelog between 4.4.3 and 4.4.4) that there were no spectacular updates in the latest stable KDE Software Compilation, I got some feedback that 4.4.4 does feel “snappier” than the 4.4.3 which is part of Slackware 13.1.

Good news (that people actually use my packages)!

It made me think again about the upcoming KDE SC 4.5 for which the second beta was released very recently (the sources at least). I had not really planned on a Slackware build for KDE 4.5 until I had access to the stable sources, which will not happen all too soon.

But if even a small (bugfix) upgrade is received so positively, some people may find it interesting or challenging enough to get their hands dirty with the new beta release. So I decided to move ahead, locate the updated and new dependencies and start building packages.

At this moment there are no kdepim packages planned for KDE 4.5. The kdepim developers decided that the current quality of their software is not high enough to be included in KDE 4.5 – they expect kdepim to be re-integrated into KDE SC 4.5.1 and will release preview versions on their own in the meantime.

The software requirements for 4.5 are not yet written down like they are for older releases, but after reading through the mailing lists I have a feeling that I will have to upgrade Qt to 4.7 in the end. There is no such Qt release yet… so at some point I will start using source snapshots from the Qt git repository.

Not right now however, because the compilation recognized my already installed Qt 4.6.2 and did not complain about that. Tonight I will finish a 64-bit build of KDE SC 4.4.85 (aka 4.5-beta2) and install that to my laptop. If that does not break everything, I will also build a set of 32-bit packages and release the lot to my “ktown repository“.

Let me know if you are interested in tying out the beta! If there is no interest, I may leave it at just the 64-bit packages and use the time to debug my VLC package (which seems to crash on VAAPI support).

Watch this space for more news, soon (I hope).

Eric