Skip to main content

KDE Future on Slackware

There has been a hot discussion on KDE's packager mailing list about KDE's new policy of splitting up the big packages into several small packages as you can see as in KDE's FTP site. In the past, KDE only break them into several packages, depending on the category, such as kdeadmin, kdemultimedia, kdepim, etc.

What's the impact? Well, for Slackware's KDE maintainer point of view, this breaks almost every SlackBuild script that they have created in the past, since now they have to rework it again from the scratch and that would requires a lot of time and efforts to create the best SlackBuild script in order to compile KDE into Slackware's native packages. Eric Hameleers aka AlienBOB wrote this on his blog and it refers to the discussion on KDE's mailing list where the discussion happened (it was on another private mailing list, but this one is the public mailing list for the release team).

Not only it breaks the SlackBuilds script, but it also causes more burden to the maintainer to maintain the packages. The situation is similar with what happened in GNOME in the past. They required a lot of efforts to maintain the packages since they were split into a lot of small packages, thus requiring the maintainer to track every released version. If you don't believe me, take a look on GSB-3.0's ChangeLog and you will understand. It's a rolling release, means it continues to change over time, unlike KDE which usually release set of changes on a monthly period. IMHO, a rolling release has it's own benefit, but for the maintainer, it would be a nightmare as they have to catch up with the latest update all the time.

So, what will happen with KDE on Slackware in future releases? We still don't have a definite answer yet, as the discussion on KDE's mailing list still on progress and also we have a discussion at LQ where Pat, Eric, and most of Slackware users shares their thoughts. If you have any ideas, thoughts, please post it on LQ as well.

One positive reaction from Pat is the fact that KDE is his favorite DE at this moment and i really hope that it would remain the same in the future. I personally a KDE lover as well and i don't really want KDE to be removed from Slackware just like what happened with GNOME on Slackware 10.2.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue