How is slackware-current looking at the moment?
 

Well I've put off upgrading to slackware 13.x with KDE4, and am still using slackware 12.2 with KDE 3.5.

Now that KDE 4 has been around for a while, and seems to be maturing quite nicely, I'm looking at simply doing an install of slackware-current with a recent KDE 4.5.x version.

Question is, how is slackware-current looking, is it good for general use at the moment? Any issues I should be aware of and so forth?

I've been "general use"ing -current for a long time now, and it has been very stable and trouble-free for me. But, I don't use KDE so if you like & use KDE, your experience may differ from mine, and you may want to wait and hear from actual KDE/-current users to see how that sounds.

Generally speaking though, -current has been zero-problems for me.

I use current since several months.
Very stable, no problems.
Idem for KDE 4.5.2

Kind regards

I am using Slackware-current (full install) with KDE on my new netbook . Before this, I used Slackware current on Asus eeepc 4g. Because it has only 4GB disk space I didn't install some of the packages but KDE worked fine for me there and with a full install its working fine now. With some of the desktop toys I had to do Ctrl+Alt+Backspace but that was (I believe) caused by those widgets.
It is generally working fine but you may encounter small problems but most of them will be easily solvable.

Some people, (me included!), have found it worthwhile to upgrade the dbus version to help with stability of Dolphin
http://www.linuxquestions.org/questi...urrent-832297/

Like the fruity one I also don't use KDE, but at the moment current is pretty solid. The only bugs I'd complain about were and are still also present in 13.1. I'm still hoping Pat will give them some attention later in the release cycle.

The thing you have to remember about running current is that it's not 'how it is today', but 'how it might be tomorrow' that you have to consider. Things can break completely out of the blue.

I'm still using 12.2
I tried 13.1 and 13.2 (kde then xfce).
One thing for sure I don't like kde anymore.

One annoying thing that I noticed on 13.2 is the behavior
of 'echo'.

I use a shell script to turn off the warning bell on the
console.
It works well with 12.* but it doesn't with 13.2

I'll wait for the next stable version and give it another try.

I've been running Slackware-current on several machines for quite some time, I don't use KDE(I'm using XFce and Fluxbox on my -current boxen). I'm not experiencing any issues. However, as this is the development branch of Slackware things can break. You are expected to be able to independently trouble-shoot issues when you run -current.

GazL, which 'fruity one' were you speaking of -there lots of fruit cases around here...

nutty as a grapefruitcake?
 

*ahem* :)

Actually, nuts come in cases. Fruits come in cakes. So above should read. "..nut cases..". However, that presents its own great mystery: where did the expression, "nutty as a fruit cake" come from? (possibly small-town U.K.? Oldham perhaps?)

No, I don't think you can blame us for that.
From Wikipedia:
http://en.wikipedia.org/wiki/Fruitcake
Relevant bit:

That's because you would have to be insane to eat a fruitcake!

In all seriousness, I have been using Slackware64-current since it came out. The only issue I've had was with dolphin crashes. Upgrading dbus seems to have fixed that. I am surprised that a dbus upgrade has not yet hit -current.

I'm running -current and 64/miltilib - current and actually have yet to experience any major wrinkles. Also, when a -current changelog
hits, it always a good thing to NOT update immediately, but watch the forum for a few days just to be on the safe side. If you're
fairly competent with linux in general....go for it!

I've had some kernel problems but nothing major with Slackware 13.0 or 13.1.