Thanks for your hard work on ktown, Alien Bob. Know that your dedication does NOT go unnoticed by this community at large, except by a vocal minority of whiners who have the wherewithal to bark demands at a person who is VOLUNTEERING HIS TIME to make the Slackware experience better.

About what demands you talk there?

You talk maybe about those three PAM config files? About those three text files?

No, nobody demanded Mr. Hameleers to act and the issue, more or less, was already solved before him to act. Eventually, someone wanted him to explain what he did.

What happened in fact was eventually the disturbance made by the true believers, in that which was discussion about what happened about autologin, which does not worked anymore for an unprivileged user.

How to discuss about the root lock which was suspected to be the main cause, without discussing about root locks and their effects?

And, BTW... since when Slackware had root locks included? Even Ubuntu does not purposely have the root locked, but disabled.

However, the biggest issue is another: if that Plasma5 requires 40 hours weekly for its maintaining by a highly qualified packages builder like Mr. Hameleers, at least in Russia those 40 hours weekly are a full time job of 8 hours daily from Monday to Friday.

Then, I understand that to maintain Plasma5 in Slackware, Mr. Volkerding should hire a really good one specially for it. Or rather to never adopt it.

I have all respect for Mr. Hameleers and his amazing efforts, but for me looks like Plasma5 is a hat too big for Slackware, hence for us.

Then, I have no regret if it will never be adopted or if it is abandoned even by Mr. Hameleers, being just too big for us.

Mr. Hameleers has a job. Slackware is a hobby for him. I appreciate him offering Plasma 5 but I'd rather him drop it than be miserable. I'm not going to argue against or in favor of Plasma 5's inclusion in Slackware since Pat has been destitute. I just want a heads up if it is to be dropped because Plasma 5 is the DE for my main computer.

Perhaps you've forgotten that less than a week ago you thought it apt to draw a connection between certain open source volunteers and Nazi death squads. But sure, you're always mild and considerate, my mistake

4 members found this post helpful.

I imagine it is the attitude that a few push when they "request" features to be added/changed. These "requests" are seeming to show that Eric has a vendetta against certain users or their desired philosophies (like being able to login as root)... but the reality is he is doing like Slackware always does and packaging things like upstream intended. If he finds that upstream has gone beyond their scope, he is usually quick to make changes, but the attacks towards him continue. But no, Eric is purposefully changing things, according to some users, when it is strictly using the defaults from upstream.

He's been dealing with people like that for many, many years. Read back through the recent threads about KDE/Plasma5 and PAM and see if it seems like people are attacking him, thinking he's pushing a no-root-login agenda or refusing users the ability to auto-login.

Why one person, who has provided so much to Slackware over the years, seems to be constantly attacked for things that he didn't purposefully do, is beyond me. Short of Pat himself, Alien Bob seems to be the person who has provided the most to Slackware over the years (at least publicly... I know there's a lot of stuff that happens behind the scenes with the other core members that may just not get publicly acknowledged) and yet there seems to be a very vocal minority who seem to find fault in everything he does and takes it as a personal attack.

Read your own posts and see if they dramatic and could be construed as demands or attacks without knowing the whole story. You can say it's cultural differences all you want (since I know that was the preferred defense of your idol, Darth Vader), but at some point, it just comes across like a jerk. Maybe it's time for your attitude to change...

3 members found this post helpful.

I apologize in advance, but I consider that someone being "volunteer" does not transform automatically that particular someone in a a holly saint which is automatically right on everything.

If history teach us something, some volunteers did really bad things and some other did really good things, some times in the same country, like was WW2's Italy, where was the fascists and the partisans.

There was the SS troops and the Red Army, both formed exclusively from volunteers. And also in Soviet Union was NKVD (later known as KGB) also formed exclusively from volunteers. There was also the Kamikaze pilots of Japan, entirely voluntary squads. And that was only some volunteers of WW2, the past is full of volunteers who did good or bad deeds.

What I want to say is that for me, someone being "volunteer" does not transform him/her in someone who I should blindly follow, because everything he/she says is absolutely sole truth.

And no, I do not talked about Mr. Hameleers, but about some programmers who believes that being "volunteers" makes them the God Messengers.

For me, that's apples and oranges.

I get it, we don't all have to agree with each other. It's your manner of communicating the disagreement that I was pointing out. We're all only human here (even the cyborgs), so it helps if we can maintain some basic courtesy, and the lack of it I imagine is much harder to take when you've been doing hard work over time. Just reflect on that is all I'm asking.

3 members found this post helpful.

Indeed! Eric created 64 bit Slackware for us. Along with being an extremely active Slackware developer he provides a wide variety of Slackware packages for us : KDE-plasma, Libreoffice, VLC, to name but a few.
Thank you Eric.

1 members found this post helpful.

There are two kinds of people. In this instance the takers wore out the giver. When stuff like this happens, nobody wins... except for your family Eric. Now you can go and spend your time with them instead of trying to please whiners on the internet.
I'd like to just echo all of those sentiments. I couldn't have said it better.

3 members found this post helpful.

Gee Thanks LuckyCyborg
....
....
NOT!

4 members found this post helpful.

Did you really think that I was only working on KDE Plasma5 packages? Spending lots of hours on that, per day? Well, no. It's not that bad by a far stretch.

These Plasma5 updates, once per month, take 2 to 3 days of hours spent in the evenings after my regular day job, to do the research about what has happened in KDE Country, how the dependencies may have changed, and then I compile, check, modify, recompile, until I have two sets of 32bit and 64bit packages.
Thanks to the people who support me with donations, I was able to buy a powerful server a few years ago, which sped up the compilation times with a factor 10 compared to the build box I used from the beginning.
Before 2018, compiling a new KDE update would actually cost me almost a week. But, since the build server would be occupied, I was free to do other things like writing documentation and creating liveslak, among others.
It's packages like vlc, libreoffice, calibre that take a lot of time to build, because they usually need patches to compile properly and I have to create those first, which also costs a lot of research time. And so on. Cutting myself loose from Plasma5 gives me back a bit of time to spend otherwise, but I will still dedicate most of my spare time to Slackware.

9 members found this post helpful.

Thank you for the update! I hate to add to a negative discussion but I want some clarity on your plans. Will there be anymore rebuilds of Plasma 5 packages in ktown if an update to Current breaks something?

Hello,


Already opened and closed. The fix will be available in KDE Frameworks 5.71.0 (scheduled for june 13).

--
SeB

3 members found this post helpful.

I think you're missing the part where Slackware doesn't just immediately update to the latest and 'greatest' software everytime something is released. The idea here is that Slackware gets the current LTS and only focuses on security update; the burnout is maintaining the bleeding edge so that's it's ready for inclusion... that's not a big deal if it only had to be done a few times prior to adoption, but this has been multiple years of maintenance. Maybe I'm misunderstanding here but I don't think this level of maintenance will or even has to continue once it's been adopted.. and like Eric said he will work on later versions with the goal of getting those adopted into future releases of Slackware.. just hopefully without this crazy long wait.

1 members found this post helpful.

Eric has also mentioned that he intentionally builds the latest and greatest stuff monthly because he likes to have it, not because it's necessary. Even for -current, it doesn't really need to be updated that frequently. Pat could drop it in today and then just update to the latest LTS once before tagging 15.0.