Tag Archives: kde413

What you do when it rains

alien

I had a great week in Bruges, Belgium. Visited the brewery “De Halve Maan” and had a tour of the new brewing hall as well as the museum with all the ages old brewing equipment. It ended with a free “Brugse Zot” blonde beer, unfiltered (you can get the unfiltered version only in the brewery’s own restaurant on-site). It really tasted great, more flavors than the bottled version.

I will try to post some of the pictures I took while roaming the city of Bruges (I nearly took 200) because it is a very pretty – Bruges is one¬†of Unesco’s World Heritage sites. But anyway, we did not have rain during our stay (a few small showers perhaps). The rain started when we went back home. With that rain, I was less inclined to go out and walk for a bit, or work in the garden. Bread making is one of the things I am doing today (using my sourdough starter which survived a week in the fridge exceptionally well). But after a week of no computing, I wanted to do something again when I got home.

So I uploaded the KDE 4.14 packages and posted the blog article, all of which I had already prepared before traveling to Bruges. And then I looked at what else had been happening during my absence. Not much really ūüôā Some new systemd related threads on LinuxQuestions.org, which I am trying to stay out of (it’s a pretty hairy discussion in there), and some more talk about Skype 4.3 which needs PulseAudio now.

Perhaps I will pick up zerouno’s successful effort¬†to package all the required 32-bit libraries along with the Skype binaries (he did not have to bother with PulseAudio then, so I think it will be more complex to make it work now)… if I find the time.

On Google+ I had attempted to find some answers to creating an OpenVZ container template for Slackware. I had hoped there would be updates during my holidays, but unfortunately the one guy (who also reads this blog of mine I believe) who has worked professionally with openvz and Slackware and whom I asked for advice did not answer. Probably too busy with his girl friend. Anyone who can help me out, please leave me a note. The G+ post contans a link to the script I wrote for the creation of that Slackware template.

kde44 I did have time this weekend to package KDE 4.13.3 for Slackware 14.1 Рas promised when I wrote about KDE 414 for Slackware-current.

The KDE 4.13.3 packages for Slackware 14.1 are available at the usual location,  http://taper.alienbase.nl/mirrors/alien-kde/14.1/latest/. Those of you who like (or need) to use a stable Slackware version will now have the opportunity to enjoy a much-improved KDE. It includes the latest Calligra office suite and also the kdeconnect package (to interface with your Android phone from within KDE)  has been upgraded and has a lot more functionality now.

calibreico¬†I also looked at the weekly update of Kovid Goyal’s Calibre package.

To my surprise he has promoted his beta version of Calibre 2 to production sooner than I expected which creates a dilemma for me. The new version 2.0.0 is no longer based on Qt4 but instead Kovid uses Qt5 for Calibre now, which allowed him to eliminate several longstanding Qt4 related bugs. My dilemma is, how should I treat the transition to Qt5 ? Should I embed the Qt5 libraries into the Calibre 2 package like I used to do long ago for Qt4 (which will greatly increase the package size) or should I request of you (users of my Calibre package) to install my Qt5 package along with the new Calibre? I would like your feedback before I decide to start building a Calibre 2 package. In the meantime, the “old” calibre-1.48.0 package will remain available in my repository.

ARM_powered_300px¬†There were two questions in my old blog pages about the status of my hardfloat ARM port. I must say, the economical crisis and the condition of our remaining parents have resulted in me having a lot less free time, and the ARM port was a victim of that. I am at a point with that port that I need to re-sync to the latest stable Slackware and then transfer the packages to a real machine… I am a bit scared of that last part. Stuart’s Slackwarearm is very successful at installing onto ARM devices, because he uses a (modified version of the) real Slackware installer for that. WIth my ARM port I am noy yet sure if I want a “Slackware-like” installation using the setup script, or create an image file which you just have to copy to your ARM device. Note that the hardware which I had in mind for my port, is the Chromebook, or tablets even, Unlike the older embedded Linux devices, those are typically equipped with a ready-made OS image instead of running an installer. But the ARM port is not dead! I just need to get my act together.

Have fun! Eric

New KDE: 4.13.3

The weekend in San Diego was a good time to get rested from my training activities (training a new helpdesk team here) and prepare Slackware packages for KDE’s monthly maintenance release 4.13.3. These packages were built for Slackware -current and have¬†not¬†been tested to work properly¬†on Slackware 14.1. YMMV

I hope that this final 4.13 release will work its way into Slackware-current. After the recent kernel updates in -current and other stability updates and functional enhancements, today saw an awesome upgrade of X.Org and the stage is now set for an upgrade from the rather stale KDE 4.10 to a new super stable and feature-rich KDE 4.13!

Then I can finally move to working on a package set for Frameworks 5 and Plasma 5, both of which got released after I started my US trip (Plasma 5 was released earlier today). The evenings in my hotel give me little opportunity to do the required testing/rebuilding/retesting. And yes, getting loaded with two pints of Stone IPA, the local alcoholic beverage, causes the brain to wander off .-)

News for all you conservative types: when moving to KDE 4.14 in august, I will build a set of KDE 4.13 packages for Slackware 14.1 to please those who prefer a stable Slackware and have no desire to run -current.

What’s new in KDE 4.13.3 ?

This is another maintenance release, so it’s targeting more stability and fixing bugs. The packages I upgraded next to KDE 4.13.3 are¬†kdeconnect-kde¬†(even more cool things to do with your Android phone) and the Calligra office suite (upgraded to the very latest version 2.8.5). Search my older posts on KDE 4.13¬†if you want to know more about what the highlights of this release cycle are.

How to upgrade to KDE 4.13.3 ?

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!

Where to find packages for KDE 4.13.3 ?

Download locations are listed below (you will find the sources in ./source/4.13.3/ and packages in /current/4.13.2/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

KDE 4.13.2 monthly maintenance release

The monthly maintenance release for KDE was announced earlier today. If you are running Slackware-current, I have fresh packages for KDE 4.13.2. These packages were not tested (and not built) on Slackware 14.1 so beware if you want to try them on 14.1.

I added¬†the promised¬†update of the libssh package in the “deps” subdirectory.¬†This enables the “sfp” kioslave again (the libssh in Slackware is too old).

What’s new in KDE 4.13.2 ?

Well, compared to Slackware’s own KDE, a whole lot ūüôā

Compared to the previous KDE 4.13.1 packages which I released last month, not much has changed as this is just a maintenance update. I did however refresh two packages outside of the KDE core: the kdeconnect-kde package and the Calligra office suite (upgraded to 2.8.3 for which the sources were available for three weeks already). Search my older posts on KDE 4.13 if you want to know more about what the highlights of this release cycle are.

How to upgrade to KDE 4.13.2 ?

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!

Where to find packages for KDE 4.13.2 ?

Download locations are listed below (you will find the sources in ./source/4.13.2/ and packages in /current/4.13.2/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

New: KDE 4.13.1. For Slackware-current users.

There is an update available for people running Slackware-current. No, not Pat’s updates, although he is quite busy lately too, and I am glad of that. Today, there is a fresh push of packages into my ‘ktown‘ repository: following on the¬†announcement of¬†KDE SC 4.13.1!

I had added¬†three new “dependency” packages for KDE 4.13 (xapian-core, qt-gstreamer and eigen3), and now for 4.13.1 I have refreshed one of the other ‘dependencies’ to match the version of the same package¬†in the KDE 4.12.5 set¬†(for Slackware 14.1). LibRaw got updated to the latest version. I am seriously pondering the update of libssh when KDE 4.13.2 becomes available in four weeks, so that the “sfp” kioslave will be built¬†again (the libssh in Slackware is too old). In fact, ¬†the libssh sources are already in the “source/deps” directory but I have not used them for now.

As already stated, I built these¬†new KDE packages¬†on Slackware-current. I have not tested them on Slackware 14.1 and will not guarantee that they are even useable on Slackware 14.1.¬†Now that Slackware-current development seems to have picked up a serious pace, it will of course bring you¬†fun and excitement to switch to the development version and join in the bug hunt ūüôā

What’s new in KDE 4.13.1 ?

In KDE 4.13, ¬†the semantic search program Nepomuk has been replaced by Baloo, which performs better and avoids the data duplication currently seen in KDE (copies of the same data, think of emails, get replicated between nepomuk, akonadi and virtuoso leading to large homedirectory storage needs). The best news for everyone who complained about Baloo, is that it is now possible¬†to disable desktop search using a checkbox in the System Settings… the developer originally thought that nobody would want to not use his software… a bit na√Įve considering the upheavals caused by the semantic search feature in KDE in earlier days. I will leave the nepomuk package in the distribution as long as the developers will ship its sources along with the rest of the Software Compilation.¬†I expect that that means, all remaining iterations of KDE 4.13. You can read more about what’s new in my previous blog post about KDE 4.13.

There were some more updates: I have added the same KDEvelop packages as were already  added to the KDE 4.12.5 package set. I have updated oxygen-gtk2 to 1.4.5 and libkscreen to 1.0.4, both these releases fix crashes in applications.

How to upgrade to KDE 4.13.1 ?

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!

Where to find packages for KDE 4.13 ?

Download locations are listed below (you will find the sources in ./source/4.13.1/ and packages in /current/4.13.1/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

Ready for download: KDE 4.13

I am starting a new cycle of KDE packaging. The KDE community announced the general availability of KDE SC 4.13.0!

After creating three new “dependency” packages (xapian-core, qt-gstreamer and eigen3), I built my new KDE packages¬†on Slackware-current. I have not tested them on Slackware 14.1 and will not guarantee that they are even useable on Slackware 14.1. If you want a taste of KDE 4.13 then please upgrade to slackware-current.

What’s new in KDE 4.13?

In KDE 4.13, major improvements are made to KDE’s Semantic Search technology, benefiting many applications. To be specific: Nepomuk has been replaced by Baloo, which performs better and avoids the data duplication currently seen in KDE (copies of the same data, think of emails, get replicated between nepomuk, akonadi and virtuoso leading to large homedirectory storage needs). A nepomuk-to-baloo migration should happen automatically when upgrading to the new KDE (according to the build log, that feature has been enabled), but I have not checked yet if that worked. Note that nepomuk is still part of the software compilation, to facilitate the migration and to allow non-KDE applications additional grace time to port their semantic search support from Nepomuk to Baloo.

KDE 4.13 can be seen as another transitional release: with Plasma Workspaces and the KDE Development Platform frozen and receiving only long term support, those teams are focusing on the transition to Frameworks 5. Still, there are interface and feature improvements to be found in several of the major applications, such as Okular (the document viewer) and Kate (the document editor) among which support for Baloo. And there is another new package: the foreign speech trainer Artikulate.

How to upgrade to KDE 4.13 ?

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!

Where to find packages for KDE 4.13 ?

Download locations are listed below (you will find the sources in ./source/4.13.0/ and packages in /current/4.13.0/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Postscript:

In two weeks, there will be another KDE 4.12 release; the final 4.12.5. Just like the previous 4.12 iterations, I will be compiling this on Slackware 14.1 and this final time, I will also publish them in the Slackware 14.1 directory of the ‘ktown’ repository, so that people running Slackware 14.1 and using slackpkg+ will automatically pick it up and get a nice upgrade to the latest super-stable KDE platform.

Have fun! Eric