balls to that, kde is the most complete DE i found so far

While my opinions of KDE will remain unspoken and unwritten, I find it extremely easy to keep it off my system. Thanks to tagfiles and slackpkg blacklist.

Dolphin and Konqueror in Slackware have many plugin viewers except for audio files.
This plugin shows the cover image in mp3 files. I didn't check for other audio types.
Since there are viewers for all other purposes, maybe this for audio files would be a nice addition.
http://kde-apps.org/content/show.php...content=145088

All you KDE "bashers" - nobody forces you to use it or even install it. Slackware works well with whatever DE you choose, from Fluxbox to FVWM XFCE, and even to 3rd-party Mate to LXQT. I'd say that is a lot more freedom than you will get in some of the major distros.
Of course, there are some serious KDE fans in the Slackware core team, so it will not be too likely that KDE will at some point be removed from the core distro. But you never know what the future brings. I will keep providing the latest KDE packages until the point where Slackware is unable to support that latest KDE.

The KDE 4 in Slackware is a mature and stable desktop environment. Sure, KDE 4.0 had issues but Slackware never shipped that version. Instead we waited until the 4 series reached the point of being production-ready and then added it (coïnciding with the initial release of 64-bit Slackware).
The same will happen for KDE 5 aka Plasma 5. Currently it is lacking some features compared to KDE 4, but the migration path from KDE 4 to Plasma 5 is free from big hurdles. There are lots of applications in Plasma 5 which are still based on Qt4 and KDE 4 core libs, and with the passing of time those will be ported to Qt5 and Frameworks 5. Inbetween, you will have a Plasma 5 desktop with all the applications available that you knew fromKDE 4. The 3rd party apps that build on KDE 4 will remain functional, and there is lots of time to migrate to Qt5.

KDE 5 aka Plasma 5 is still under development, which means you won't see it in Slackware for at least another year. There will be some dependencies that I am trying to avoid: systemd (still easy to avoid in KDE but not adding it causes a minor loss of functionality) and wayland (the compilation of KWin for X11 has a hard dependency on wayland even when it does not use wayland at runtime).

In the meantime, those of you who like working with KDE can download and install the latest KDE 4, and next week the latest KDE 5 (Frameworks 5.6.0, Plasma 5.2.0 and Applications 14.12.1 combined with the core KDE 4 libs).
See http://alien.slackbook.org/blog/usin...king-on-kde-5/ for my story on KDE 5 for Slackware and http://taper.alienbase.nl/cgit/ktown/log/?h=5_15.01 if you want to follow my KDE.SlackBuild development closely.

Finally, several of you are boldly stating that KDE is a maintenance burden comparable to Gnome. Well, let me tell you that it is not. With every new major release (KDE 4, Plasma 5) there is a one-time effort to get the KDE.SlackBuild build framework adapted but then it is easy as pie to create packages and keep up to date. Adding new packages is also very easy. Effectively, I have taken the "burden" away from Patrick.

16 members found this post helpful.

I don't use KDE per say directly, but a lot of the tools that come with KDE are very handy and irreplaceable. Ripping out KDE from Slackware would be like ripping off one of your own legs.

Good to know this. But the "official" KDE is still 4.10.5. Even in current. I am confused.


Cheers

1 members found this post helpful.

Such as?
Just curious

Okay, you are right - that is indeed a major breaking point.

I didn't really think about the future. When KDE5 is released, the 4.x branch will be rotting like it happened with 3.x.

I would be very happy about Trinity - that DE has matured over more than a decade and it's still KDE. KDE 3.x was my favorite window manager as long as I could use it and I would be happy to go back.

I hope you didn't construe my comment as bashing. Because my point was that, whatever anyone's opinion of (or usage for) KDE, it is a simple matter to just never install it. Obviously, lot's of Slackers use KDE, so it is a excellent inclusion in Slackware (my opinion). My choice to not use any DE at all is not a reflection of any kind of opinion I have about your work to maintain packages for it. I wouldn't use Slackware if I didn't have a high opinion of your work and the work of all the Slackware developers.

If it was construed as bashing, feel free to let me know and I will try harder to restrain and filter my comments.

Not at all. Your statement was clip and clear: you do not use KDE but also refrain from negative comments. That's OK with me.
The bashers are those who don't (want to) use KDE and come up with all sorts of real and bogus reasons for ditching it from Slackware.
Again, if you don't like it, no one is forcing it upon you. Like j_v stated: simply do not install it! The rest of Slackware will not be negatively affected by its absense.

2 members found this post helpful.

Could rxvt-unicode and rxvt-unicode-256color be added to termcap and terminfo please?

termcap is needed to avoid the scrolling
< the scrolling off to the left on very
< left on very long lines.

And everything else needs terminfo.

Eric has had newer versions available in his ktown repo for quite a while. I'm running his 4.13.3, which is the latest for Slack 14.1, and he has 4.14.3 for -current (not including his KDE5 testing area). Eventually, Pat will roll Eric's updates into -current, but he usually does them few and far between, while Eric makes continuous updates to the ktown repo.

http://alien.slackbook.org/ktown/

fakeroot needs to be added

Does fakeroot even still build on modern systems?

it builds fine on Slackware