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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Tuesday, 13 October 2020.
Plasma 5.20
New and improved inside and out
A massive release, containing improvements to dozens of components, widgets, and the desktop behavior in general.
Somehow I hear some faint echo of an old song running through my head.....
"If you wanna be happy for the rest of your life
Never make a pretty woman your wife
From my personal point of view
Get an ugly woman to marry you!"
I'm pretty sure it was an argument to be less concerned with glitz, glamour, and ornamentation and be more focused on function. Beauty is a state of mind and can always be created, adapted and upgraded. Function is binary - either there or it's not.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Originally Posted by enorbet
..... Beauty is a state of mind and can always be created, adapted and upgraded. Function is binary - either there or it's not.
Beauty is fleeting. Personality (function) is of greater importance.
I don't know about the kids today, but when I was younger, thinner and had more hair, we (men) put women on a pedestal. The prettier they were, the higher the pedestal. After spending a great deal of time in another part of the world, where a disproportionate percentage of the women are drop-dead gorgeous, I learned that many of those adages we were told as children are actually true. "You can't tell a book by it's cover" being the first one that comes to mind.
OTOH, kde4 (appearance) is holding up well, given its age.
Last edited by cwizardone; 10-15-2020 at 09:49 AM.
Reason: Typo.
I tried to build Plasma Frameworks 5.75 as a prelude to building Plasma Desktop 5.20 by using Alien's source SlackBuild. Everything went ok after moving kdav to tier4, but near the end krunner failed to build. I'm using current and the experimental gcc 10.2.
The error output is quite long so I put a pastebin here:
I tried to build Plasma Frameworks 5.75 as a prelude to building Plasma Desktop 5.20 by using Alien's source SlackBuild. Everything went ok after moving kdav to tier4, but near the end krunner failed to build. I'm using current and the experimental gcc 10.2.
The error output is quite long so I put a pastebin here:
Any hints on how to get over this would be really appreciated.
Why did you move kdav to Tier 4?
krunner builds fine here. I have kdav in Tier 3, well before krunner. I am also using GCC 10. I am building on a clean Slackware64-current without KDE.
Look here if you want to know what Tier a Framework belongs to: https://api.kde.org/frameworks/ . You'll find that the developers place KDav in Tier 3.
Look here if you want to know what Tier a Framework belongs to: https://api.kde.org/frameworks/ . You'll find that the developers place KDav in Tier 3.
I moved kdav to tier 4 since its build failed, complaining that KIO was a missing dependency. Given the reports maybe I should put it back on tier 3 but below KIO.
Thanks for the pointers!
Well, the problem must lie somewhere else. I moved back kdav into tier 3 (I put it last just to be sure) and built fine. But krunner still fails. Well, back to 5.72 and stay put.
Well, the problem must lie somewhere else. I moved back kdav into tier 3 (I put it last just to be sure) and built fine. But krunner still fails. Well, back to 5.72 and stay put.
Did you remove the patch from krunner. Open patch/krunner.patch and comment it out. It is no longer needed.
I am still curious as to why you moved kdav to tier 4.
Did you remove the patch from krunner. Open patch/krunner.patch and comment it out. It is no longer needed.
I am still curious as to why you moved kdav to tier 4.
1. Thanks for the patch suggestion. I will try it out.
2. It was my fault. Using AlienBob's SlackBuild I saw that kdav failed to build complaining that kio was missing. Seeing that kio was in Tier 3, I thought that perhaps moving kdav out to Tier 4 would solve the problem.
Well, kdav then got built, but moving it to tier 4 was unnecessary. Just putting it out below kio on Tier 3 did the same trick.
EDIT: After removing the krunner patch, everything built fine. I'm typing this using Frameworks 5.75. Thanks for the suggestion!
Now let's try our hand at Plasma 5.20.
Last edited by sombragris; 10-18-2020 at 09:16 PM.
Oh well. There's a weird error in systemsettings 5.20
Code:
Building from source systemsettings-5.20.0.tar.xz
mkdir: cannot create directory ‘build’: File exists
CMake Error: The current CMakeCache.txt directory /tmp/kde_build/plasma/systemsettings-5.20.0/build/CMakeCache.txt is different than the directory /home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0/build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
CMake Error: The source "/tmp/kde_build/plasma/systemsettings-5.20.0/CMakeLists.txt" does not match the source "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
CMake Error: The source directory "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** [Makefile:908: cmake_check_build_system] Error 1
CMake Error: The source directory "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** [Makefile:908: cmake_check_build_system] Error 1
plasma failed to build.
Any ideas on how to get unstuck here? Thanks in advance!
Oh well. There's a weird error in systemsettings 5.20
Code:
Building from source systemsettings-5.20.0.tar.xz
mkdir: cannot create directory ‘build’: File exists
CMake Error: The current CMakeCache.txt directory /tmp/kde_build/plasma/systemsettings-5.20.0/build/CMakeCache.txt is different than the directory /home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0/build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
CMake Error: The source "/tmp/kde_build/plasma/systemsettings-5.20.0/CMakeLists.txt" does not match the source "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
CMake Error: The source directory "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** [Makefile:908: cmake_check_build_system] Error 1
CMake Error: The source directory "/home/jr/src/releaseme/releaseme/plasma/5.20.0/systemsettings-5.20.0" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** [Makefile:908: cmake_check_build_system] Error 1
plasma failed to build.
Any ideas on how to get unstuck here? Thanks in advance!
Please download systemsettings-5.20.0.1.tar.xz , replace the previous tarball and try again.
Because the original version was wrong packaged, containing the "build" directory used for build, and resulting in this error.
I for one, I modified kde.SlackBuild to remove automatically the "build" directory fro sources when building a package, but maybe is simpler to just update the tarball.
Last edited by LuckyCyborg; 10-19-2020 at 12:23 AM.
Please download systemsettings-5.20.0.1.tar.xz , replace the previous tarball and try again.
Because the original version was wrong packaged, containing the "build" directory used for build, and resulting in this error.
I for one, I modified kde.SlackBuild to remove automatically the "build" directory fro sources when building a package, but maybe is simpler to just update the tarball.
I tried to remove the build directory and the building still failed but in a different way. However, downloading 5.20.0.1 did the trick. Thanks for the pointer.
I'm now running Plasma 5.20 without any problem. Thanks to everyone!
By the way, I just built KBibTex using AlienBob's system. It was a matter of adding the relevant source in applications-extra, updating the relevant modules file and providing a slack-desc. He is a true master. Thanks Eric!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.