I believe it, but I try my hardest to not run -current on my main desktop. I don't like rebooting it as often as is needed when following -current (and I'm pretty bad about keeping up with the updates and trying to rebuild all my 3rd-party applications when needed).

I'm looking forward to trying out Plasma5 when 15.0 is released (that is with the belief that it does get added before the next stable release).

Pat, please consider adding fwupd, perhaps to /extra. Firmware is a continual thorn for all users. The package is available in SBo.

Thanks. :)

The short version to my question is, is there any real technical advantage to KDE vs. Xfce, or does it just boil down to personal preferences?

Back on 1 December I did a fresh install of -current and then immediately installed KDE-5 and Xfce-4.14 and bounced between them, using one or the other for several hours or several days before switching back to the other again.
Can't say I really cared for either one of them.
Yesterday I did another fresh installation of -current, but this time stayed with Xfce-4.12 and KDE-4. As to appearance, KDE-4 beats the socks off of KDE-5, and it is easier to get Xfce-4.12 to look like something I can live with vs. 4.14.
Each have their "pros and cons" but, is there really that much differnce between the two? Techinally, that is?
For this purpose, i.e., the question, the number of "built-in" kde applications is not an consideration.

For some it is absolutely preference, for me, it is technical and preference. I've found XFCE lacking in several factors that were important to me (although, the last time I did any serious digging with XFCE was with 4.10... I haven't dug through 4.12 much, just tweaked a few things I needed, and I haven't touched 4.14 yet). I ran into issues with conflicting power control settings. It's been a while since I had to deal with it (and maybe the problem is solved with 4.12 and it was a major issue with me with 4.10 and that's why it's stuck in my mind), but I remember needing to use something not from XFCE to get my monitors to go to standby after a certain period of time.

And now, I currently have to uncheck the "Mirror Displays" option every time my monitors come out of standby. It boots up with both monitors normal, but whenever the screens go to standby, when they come out, they're mirrored. I found other reports of it online, but the only fix I found (manually setting the screens location in an xorg conf file) doesn't make a difference on my system. This is by far, the most frustrating thing with XFCE right now, because I have to change it every time I wake up the monitors. This could very well be an issue with xorg/mesa for my video card, but I never had anything like that happen within KDE.

I also find Thunar and Terminal quite lacking in comparison to Dolphin and Konsole (but I know that some really prefer Thunar, so it's likely a personal preference kind of thing). And the default theme runs into display issues with some KDE programs (mainly when renaming with krusader, it would show the old text under the new text and it was almost impossible to see what you're typing)... I was able to resolve this by selecting a new theme (but then I guess I shouldn't expect a gtk theme to work flawlessly with a QT app).

I'm sure a lot of it also comes down to familiarity. I've been using KDE since the v3.x days and I've grown used to how things are laid out and what I need to tweak. I tend to prefer KDE programs over others. KDE also requires a lot less tweaking out of the box to get it to where I like it, where XFCE usually has me stumbling around menus or google searching how to change the things that are annoying to me. I just tend to feel frustrated when trying to tailor XFCE to my needs, where KDE tends to not invoke that frustration nearly as often.

I suggest make mozjs name without version reference...

mozjs56 --> no
mozjs60 --> no

mozjs-60.x.x

with this , people can make easiest upgrades with upgrade-all , no need find mozjsxx removed ..mozjsxx added ...thats incongruent.

I never understand, the name of this package ..why not iw5-5.1 , binutils40-40.xx ... not good.

Its only suggest.

KDE-5 does have the ability to set a gtk theme for your gtk based applications.
Trouble is, when you start playing with theme settings for KDE/QT it scrambles your Xfce theme settings. The only way I can get around it is to delete the configuration files, start over with Xfce and don't dare to open KDE-5, again.
OTOH, I've alway had the feeling, but it could all be subjective, that KDE does a better job of handling the audio and video.
I bought my first Linux distribution in Spring of '95 or '96, and, of course, it was Slacxkware. :)
I was a big fan of KDE up to 3.5.10, but then we all know what happened with KDE-4.0. IIRC, it was KDE-4.13.6 befoe I felt KDE was worth using again, but by then I had used Xfce for so long I kept, and keep, going back to it.
Between Dolphin and Thunar, I agree Dolphin is the better of the two. Xfce's Terminal takes some getting use to, but it does the job.
After using Xfce for so long I've found alternative applications to everything I liked about KDE, so other than K3b, I rarely use anything from KDE while in Xfce. Oh, I do on occasion run "Sweeper."
:)

I requested this also, but as it was explained the naming is like gtk (and gtkmm) for good reason. I need both mozjs52 and mozjs60 and it is a lot nicer with them named this way for using multiple versions on the same system, just like gtk.

but slackware use only 1 , sbo can do another needed with numbers if want ... its good idea when a system have two packages of same with different abi or something, but slackware for now use only 1 mozjs pkg.

I hate to be "that guy", but all distros do it like this, including Slackware 14.2 with 'js185-1.0.0-x86_64-1.txz'
(bet you didn't even know that they are the same thing)

I also imagine that there will be no more updates to mozjs once 15.0 is released. So it will stay at mozjs60 or whatever version it lands on.

Personally , im not have problem with mozjs3000 ..or something, cause i read the changelogs frist , but see the forum , not all people read and upgrade ....in some case, for me , can do mozjsWHATEVER.

i go slackbuilds, and ho ho ho ..mozjs ..without numbers.
https://slackbuilds.org/repository/1.../?search=mozjs

Peace & love.

I suggest for community , not for me.

Not all people should be running current. Especially if they are not reading the changelog.

So I suggest you let it go because I doubt that it is going to change.

See this: https://www.linuxquestions.org/quest...ml#post5928932

Personally I find updating -current every few days much less hassle than trying to get everything I need/want running properly with 4-year-old system libraries, but YMMV.

Hello.
Is there a todo checklist what have to be done to release Slackware 15.0?
Thanks.

doxygen 1.18.17
http://www.doxygen.nl/manual/changelog.html
http://doxygen.nl/files/doxygen-1.8.17.src.tar.gz

It seems to build fine on -current.

Not a public one as far as I know.