SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You do not have to install KDE if you do not like it. I am running Slackware without KDE and everything works as expected. You do not need KDE.
I don't even touch that crap. The problem is different...
KDE slowed down Slackware releases what made a lot of (majority) users to assume that Slackware is dead now. And these thoughts are pretty much reasonable.
I don't even touch that crap. The problem is different...
KDE slowed down Slackware releases what made a lot of (majority) users to assume that Slackware is dead now. And these thoughts are pretty much reasonable.
This maybe true and I am not a fan of KDE either, however, from what I have seen here in this forum it would probably be a big issue for a lot of users - maybe even a dealbreaker.
This maybe true and I am not a fan of KDE either, however, from what I have seen here in this forum it would probably be a big issue for a lot of users - maybe even a dealbreaker.
Throwing GNOME away wasn't a dealbreaker though. The situation with KDE will be worse and worse in the future.
A folk who registered @ LQ one week ago says to Patrick "drop the will-be flagship desktop of Slackware 15"! Thanks ialexand, you made my day. There really should be a smilie for ROTFL
I cannot really comment on the GNOME issue since I did not use Slackware when that happened. However, GNOME and KDE were always the two "big" desktop environments. After GNOME was dropped there was still one big DE left. I do not know if any distro can afford to supply only lightweight desktop environments.
I cannot really comment on the GNOME issue since I did not use Slackware when that happened. However, GNOME and KDE were always the two "big" desktop environments. After GNOME was dropped there was still one big DE left. I do not know if any distro can afford to supply only lightweight desktop environments.
Patrick's "special" vision of his distribution cannot afford things like GNOME or KDE. Just a proven reality.
@ialexand: your opinion on this topic doesn't matter at all to Patrick. Assuming you are realistic enough to realize that, what is really the purpose of this thread? Just bored? Or just in need to express your frustration?
Last edited by Didier Spaier; 04-08-2021 at 06:38 PM.
I know this is probably a troll post, but I felt like people could appreciate the below...
Quote:
Originally Posted by ialexand
KDE slowed down Slackware releases what made a lot of (majority) users to assume that Slackware is dead now. And these thoughts are pretty much reasonable.
This is your speculation with no solid information backing it. There were a lot of big changes with the soon-to-be-released 15.0. Any one of those could've been the cause of the extended development or, more likely, it was a combination of many things.
In fact, just looking at the changelog, PAM was likely a much bigger factor on the delay of 15.0. vtown for Plasma5 was in testing/ for just over a month (3 NOV - 7 DEC) and about 2 weeks of that included adding xfce-4.14 into vtown with Plasma5. PAM took over 3 months in testing/ (after who knows how many months they were testing it internally) and Pat said he wanted to merge it into the main tree in a day or two. It was added in testing on 12 FEB and finally moved to the main tree on 18 MAY.
It seems if Pat wanted to add PAM to the main tree within a day or two of going in testing/ and it took over 3 months (95 days) to actually happen, that PAM was probably the single biggest issue that caused a delay with 15.0 (with lots of others also contributing).
Long story short, we simply don't know why 15.0 took so long. Anything anybody states on the reason for the delay (including this post) other than Pat (and maybe his core dev team) is speculation... in other words, guessing.
@ialexand: your opinion on this topic doesn't matter at all to Patrick. Assuming you are realistic enough to realize that, what is really the purpose of this thread? Just bored?
If it matters or not - you don't decide it. You already expressed your view on the topic, and you don't need to repeat it again and again. So mind your business and don't behave like a clown.
I know this is probably a troll post, but I felt like people could appreciate the below...
This is your speculation with no solid information backing it. There were a lot of big changes with the soon-to-be-released 15.0. Any one of those could've been the cause of the extended development or, more likely, it was a combination of many things.
In fact, just looking at the changelog, PAM was likely a much bigger factor on the delay of 15.0. vtown for Plasma5 was in testing/ for just over a month (3 NOV - 7 DEC) and about 2 weeks of that included adding xfce-4.14 into vtown with Plasma5. PAM took over 3 months in testing/ (after who knows how many months they were testing it internally) and Pat said he wanted to merge it into the main tree in a day or two. It was added in testing on 12 FEB and finally moved to the main tree on 18 MAY.
It seems if Pat wanted to add PAM to the main tree within a day or two of going in testing/ and it took over 3 months (95 days) to actually happen, that PAM was probably the single biggest issue that caused a delay with 15.0 (with lots of others also contributing).
Long story short, we simply don't know why 15.0 took so long. Anything anybody states on the reason for the delay (including this post) other than Pat (and maybe his core dev team) is speculation... in other words, guessing.
Too many words... You probably forgot many years of Allien's efforts before Plasma went to -current and still problematic.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
