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 know what else works, if you have slackpkg+ installed?
Code:
slackpkg remove ktown
You know what will work, without slackpkg+, if and when Plasma5 replaces KDE4 in -current?
Code:
slackpkg remove kde
Jeez laweez, the amount of FUD being spread about Plasma5 in this forum is beyond ridiculous.
For now, the Plasma5 is in ktown, but after it will be merged, apparently many dependencies will be put in other places like l/ series, which will make much more dificult to be identified and removed. At least that is what I read.
I think the people does not hate Plasma5, but they hate the idea to spend months to discover how to remove completelly every bit and bolt of it. For example, did you know for what is good "milou" ?
Give them a way to cleanly remove it in matter of minutes, and you will make everyone happy.
Last edited by ZhaoLin1457; 07-05-2018 at 07:03 PM.
By that logic, kdelibs4 would be in l/ currently, and it is not. There are plenty of examples of libraries that are more tied to KDE(4) that are not in l/. Don't be ridiculous.
By that logic, kdelibs4 would be in l/ currently, and it is not. There are plenty of examples of libraries that are more tied to KDE(4) that are not in l/. Don't be ridiculous.
Apparently, right now there (in l/ series) is the Qt4 and probably some Qt4 and KDE4 only dependencies.
From what I read, the anti-Plasma5 people expects the situation to become much more worse from their point of view, after the Plasma5 is merged.
I think this is the root cause of those protests against it.
Last edited by ZhaoLin1457; 07-05-2018 at 07:08 PM.
Wouldn't it be nice if we could have one thread where KDE is discussed and you and Darth Vader do not pollute it with this nonsense? These complaints are ridiculous and have already been discussed ad nauseum. Go read the original post. This is a support thread. It is not the place to continue your flame war.
I come here to show something which I think is useful for certain people, my plasma5cleaner script and I explained what I think is its usefulness when I was asked. Punctually.
Where did you see complaints? Rather I think that I have an idea how to calm the spirits.
I am not pro or against Plasma5 and from a bit of spirit of adventure and curiosity, I even use it curently.
Last edited by ZhaoLin1457; 07-05-2018 at 07:46 PM.
IF you suspect that your Plasma5 applications does not show the bold characters where you suppose to be, you can fix that editing manually its configuration files from ~/config, looking for
Code:
,Regular
That should disappear, then you can restart your DE (i.e. logout/login) and everything will be fine. Of course, until you modify the font settings somewhere.
Since when is there a problem to edit a fucking file in Slackware?
Since when is there a problem to edit a fucking file in Slackware?
Files. Any Plasma5 application which saves font information in its local configuration file will be affected by this erroneous saving of information, then after it will not be able to read.
The problem is that is is not supposed you to manually edit those files. It is a bug.
Anyways that's the workaround in case someone wonder what the heck happens. And it is a bit strange as the effect.
However, please breathe, I will not respond to your tentative to provoke, then later to be blamed (again) of "pollution".
Last edited by Darth Vader; 07-05-2018 at 08:05 PM.
No, I don't believe that would work. "install ktown" is correct.
According to TFM, "install-new" doesn't take arguments, and only tracks the main Slackware repo.
"install ktown" basically says, install the whole repo; if there are items already installed, skip them; and if there are missing items, install them as well.
Last edited by Poprocks; 07-05-2018 at 08:07 PM.
Reason: Clicked submit before done
install plasma5, then need plasma5cleaner? t'would be better to just reinstall slackware.
Of course not. If you have slackpkg+, you can just use "slackpkg remove ktown".
Otherwise, just remove all the packages from ktown. ZhaoLin1457's script will work, but it's really not necessary to have a "script" that just runs removepkg on a number of packages. Just fetch the list from Alien's server, and run removepkg on all of them. Easy peasy.
I highly recommend slackpkg+ though if you're going to be playing with ktown. Highly simplifies the process.
Files. Any Plasma5 application which saves font information in its local configuration file will be affected by this erroneous saving of information, then after it will not be able to read.
The problem is that is is not supposed you to manually edit those files. It is a bug.
Anyways that's the workaround in case someone wonder what the heck happens. And it is a bit strange as the effect.
However, please breathe, I will not respond to your tentative to provoke, then later to be blamed (again) of "pollution".
I gave you the link to the bug report in the other thread. Go there and spread your FUD about Plasma5.
install plasma5, then need plasma5cleaner? t'would be better to just reinstall slackware.
This plasma5cleaner is supposed to remove any known Plasma5 package or its dependency, including Qt5.
Maybe its usefullness is not too high now, but in future, after the Plasma5 is merged in Slackware, apparently some packages will be put in another places than kde/ and may be more difficult to be identified.
So, even if the user deselect that "kde" switch on a clean install, apparently some parts of Plasma5 dependencies and the Qt5 will be still installed.
That could be dissapointing for some people. Let's remember that there are people who prefer a "de-blobled" kernel with no firmware, even for us it is something strange.
I thought that offering a way for a future full "de-plasmafication" is useful and will calm the spirits.
Last edited by ZhaoLin1457; 07-05-2018 at 08:39 PM.
You literally have NO IDEA what Pat Volkerding will choose to put in l/ and what he will choose to be in kde/. You're just speculating and making major assumptions.
So, even if the user deselect that "kde" switch on a clean install, apparently some parts of Plasma5 dependencies and the Qt5 will be still installed
Some time ago I thought server doesn't need kde, did a clean install deselecting kde, found out couple things did need couple things X or kde, not sure it's been a while, installed those parts and was good to go
Maybe a plasma5cleaner would be better after plasma5 dust settles?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.