Hmm...

Attached Thumbnails

 

2 members found this post helpful.

BTW, this one of 2300 files is one of the smallest ones. I have projects even about 8000 files.

Also, for me, sticking with 14.2 is, well... problematic. As it hate my hardware and my hardware hate it.

OK, maybe I can solve that, backporting the kernels and the graphics stack from today -current.

1 members found this post helpful.

That's our boys!

PS. You guys better read carefully this http://lists.qt-project.org/pipermai...ay/029902.html

Yep, they have plans for Qt6. For this year. And the Plasma will go along. They will rewrite it again from zero.

IF the Slackware -current adopts now the Plasma 5 for v15, I guess it will be already obsolete in the next Slackware development cycle.

So, we will have the unique case where the Plasma 5 will be shipped only by Slackware 15.

My crystal ball says that in several years we will do polls Plasma 5 vs. Plasma 6. For v15.1

1 members found this post helpful.

Have you considered Trinity Desktop?
https://www.trinitydesktop.org/appli...hp#development

1 members found this post helpful.

Sure. Also I consider seriously the "Quadrinity" Desktop for work.

I'm not so inclined, but after reading this thread I found mentioned quite a lot of the concerns and problems that I had in getting KDE 5 built and configured. Let's NOT go there, but Slackware and B/LFS are probably the last traditional GNU/Linux distributions (as opposed to the so-called "modern" systemd/Linux variants). So if there gets a point where KDE5 will not run with the traditional LFS base then it probably won't work on Slackware without heavy modifications, either. And some parts seem to be headed that way.

Slackware is the distribution that people turn to when things are expected to "just work" and thus far it has all of the tight integration needed to make that happen. KDE5, well, doesn't "just work," and folks like to add a "yet" there, but will it ever?

Not to mention rebuilding a newer point release of KDE5 (kdelibs and plasma user space) sometimes requires newer versions of graphics packages (Mesa, X, ...) so it's not always even possible to fix bugs without an entire OS spec bump.

3 members found this post helpful.

Care to share which part you are talking about? I would not be able to mention any at this point in time.

For slackware-current that is not an issue. And I have been building KDE5 packages for Slackware 14.2 (which was released one and a half year ago) until december 2017 without the need for X.Org or mesa updates. So I think it is not as bad as you think.

1 members found this post helpful.

[Just being nosey ... ]

What kind of work flow requires 2300 ( or as you say in a later post, 8000 ) interactive graphical edit sessions ?

Or is this some sort of Kate Scripting than cannot be done with traditional commandline tools ?

[/Just being nosey]

Thanks !

-- kjh

Qt6 is supposed to be source compatible with qt5, so it isn't a given that the KDE developers will need to start from scratch.

The web development.

If you are curious, you can start by counting the files from a Moodle: 16937, for example.

But there are many web applications much more complex than it.

PS. For fun, you can count also the files from your current kernel sources: 67232. Not only in the web development are tons of source files.

PS2. For example, only the Laravel Framework kernel alone has 887 files.

Specifically I'm talking about session management and getting Shutdown, Reboot, Hibernate, and Suspend to show up AND actually work. There was discussion about this here. I unfortunately could not get the desired behavior even by trying the suggestions in this thread regarding 'startkde'. If this has actually been fixed (in the sense of not needing any logind implementation whatsoever) since then, then that would surely be a plus.

In my experience there was a spec bump needed in going from KDE 5.5 to 5.8 - although the packages compiled without error, keyboard and mouse flat out failed to work, and text input was garbled, on 5.8 until I upgraded the underlying system. BLFS specifically asks for "Mesa built with Wayland" for building the Plasma part of KDE 5. I suspect this is where things can get messy - maybe Mesa built this way has issues. Perhaps you have found a way to avoid this (and thus skipping the kwayland{-integration} packages)? If so that would probably give much more flexibility and stability with adopting new versions.

Yeah, but why do they all need to be open at the same time?

Long story short: I need to open a very large number of files in a editor. FOR WORK!

What I do? Why I do that? It is my own business. And precisely is not your business.

I just can't imagine a situation where it would be more productive to have all of them open at the same time than only the ones you are working on, but as you said, it's your own business.

1 members found this post helpful.