Darth_Vader: by your logic, Pat should stop including vim, since it averages two releases a day.

Also: one release a month isn't exactly an overwhelmingly rapid release schedule.

1 members found this post helpful.

Can we not spam this thread with arguments about Plasma 5? This has already been discussed ad nauseam in other threads, and you can always resurrect one of them if you want to continue.

6 members found this post helpful.

Surely not, if we talk about VIM, but when we talk about an entire ecosystem of independent applications and frameworks, compared with the Slackware's biannual release cycle, this is really overwhelming.

Also, to note that I do not talk about "stopping including" the KDE or Plasma, but giving it a more proper environment to evolve?

You will not trust a very Patrick's KTown or a separate Plasma 5 DVD? Myself I will do.

This is a proposal for -current, BTW...

nano-2.9.2:

https://www.nano-editor.org/news.ph
https://www.nano-editor.org/dist/v2.9/nano-2.9.2.tar.xz

I think I understand where points @Darth Vader.

Having a separate official ktown will permit to Patrick Volkerding to leave its handling to one of his lieutenants. I cannot see one other than Eric Hameleers, though.

Also having a separate tree, will permit to give to KDE5 more releases, i.e. two times per year.

Mainly will profit from this exactly the KDE5 users.

Oh, give it a break. You know what I mean when I type KDE5.

And Pat only needs to push patches for serious issues. How many patches has he pushed to the 4.4 kernel compared to how many were put out by the kernel devs? There's been over 100 patches from the kernel devs for the 4.4 series and 14.2 has had 6 kernel patches. Stable Slackware releases don't need their software to be kept up-to-date... they just have serious bugs/vulnerabilities patched when they are found.

That's exactly what you're talking about. It would no longer be in the main distro. And then you're saying Pat should keep the first repo of official software outside of the install media? That would mean he'd likely need to add a way to add it and keep it up-to-date with the distro (maybe incorporating slackpkg+ as an official program?).

Or, he could just include it in the official release like he has with previous KDE versions and only provide patches when necessary, and then others who want to track the monthly releases could use ktown.

Stable Slackware releases are supposed to be stable (hence the name). "Evolving" software doesn't belong... but Eric provides ktown to those that are willing to use evolving KDE software releases.

But I'm not going to derail this thread further. If you want to continue to discuss this with me, open a new thread or PM me.

2 members found this post helpful.

I think @Darth Vader mentioned a separate DVD for shipping the KDE5.

If there are so many KDE5 fans, releasing several times per year those official KDE5 compilations on DVD would likely to increase the company revenue.

Or maybe there are just few vocal fans of KDE5 and the huge majority use lighter alternatives?

According with https://www.linuxquestions.org/quest...-a-4175614638/ only 69 users voted for KDE5.

That is a sentence without value.
An absolute number has no meaning. If you check that post, the question was "do you prefer KDE4 or KDE5" and with just these two options, 72.63% chose KDE5.

2 members found this post helpful.

Thank you, I will correct:

From the supposed Slackware community, only 95 users looks like was interested by KDE at whole, either v4 or v5.

I say "only" because a personal wild guessing is that the number of those using Slackware is much larger than that.

Want to take a guess at how representative the turnout of a poll on an internet forum is of the worldwide Slackware community?

1 members found this post helpful.

I'll take the opportunity to repeat my recent suggestion about promoting, at some point in time, some well-known stuff from SBo/repository/*/academic, like R, Octave or Maxima (maybe OpenBLAS too) into official Slackware packages.

But my main reason to write this post is actually to say big thanks to Slackware team for all their sane choices related to packaging. Namely, recently I was involved in an intensive round of testing of some codes that I'm working on for different distributions, mostly CentOS/Fedora, then for openSUSE, and also a bit for Debian/Ubuntu. I typically don't do that part of the work, but at the end I was delighted with opportunity to learn about progress in container solutions, in our particular case about Singularity, that made it possible to actually do all of the work on a Slackware system, using lightweight containers for mentioned distributions, all supplemented by flawless handling of some complicated stuff like using host GPU(s) for computations from the container, or integration with host MPI installation. All together, indeed a perfect setup for a developer to build and test code for different distributions. On the other side, I was reminded how package handling in each of mentioned distributions is an absolute nightmare. Namely, when one works with containers the goal is typically minimal install, but with all of these insane dependency resolution chains, you just end up with installing half of the packages one way or another. Adding insult to injury is this sick practice of splitting each piece of software into multiple packages, like foo-base, foo-devel, foo-libs, foo-noarch, foo-with-bar, foo-with-baz, etc. etc. So again - thanks Slackware team for keeping it simple and manageable.

6 members found this post helpful.

I do use a lighter alternative, but KDE Frameworks 5 is an important part of that alternative.

1 members found this post helpful.

You'll never guess which DE Mr. Volkerding uses.

2 members found this post helpful.

Is LuckyCyborg a pseudonym for Darth?