Building the KDE4 for Slackware 15.0 in the KTown style - a build based on the PBSLACKS patches
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.
The code bellow seems to give results most similar with what does the module present on KInfoCenter from Plasma5 .
My friend have also an explanation: some GL renderers (i.e. the NVIDIA blobs) may put a long information between parenthesis.
Code:
const QString Module::getGraphicsProcessor()
{
QGLWidget* glWidget = new QGLWidget;
QGLContext* glContext = (QGLContext *) glWidget->context();
glContext->makeCurrent();
QString ret = QString::fromUtf8(reinterpret_cast<const char *>(glGetString(GL_RENDERER)));
delete glWidget;
// Parse the result.
ret = fancyString(ret);
// It seems the renderer value may have excess information in parentheses ->
// strip that. Elide would probably be nicer, a bit meh with QWidgets though.
ret = ret.mid(0, ret.indexOf('('));
return ret.simplified();
}
The result of this update can be seen on the attached screenshot.
Last edited by LuckyCyborg; 05-13-2023 at 01:41 AM.
I'm currently testing a repo
I included it in my slackpkgplus.conf
For now, the only issue is the name kde/ of your directory, that is blacklisted for slackware64 repo
I took the liberty to rename it kde4/
I'm generating the md5sum of the tree, I also have a gpg key
If it sounds good, I will give you my feedback, and maybe it will be a good idea to ask Tadgy for hosting it ?
EDIT:
Another issue, more or less major for a repo
The patches/ serie
Unfortunately official kde packages cannot be blacklisted from this patches/ set because they are not in a kde/ directory anymore
fortunately, there will probably be no more patches for KDE (except for krusader at the moment, which is the one that allowed me identify this problem)
I will be very happy if you manage to make a repository for this kde4town.
However, please bear in mind that one of fundamental ideas behind kde4town is to have a directories structure like the original KTown made by Mr. Hameleers. And the KTown had a kde directory for packages, and so on.
Also, please note that I have the intention to add also a i586 build for the "final release" for Slackware 15.0 - which rather depends on when @BrunoLafleur finishes the NetworkManager integration, which is heavily modified by him.
Finally, please note that I have the intention for this weekend to add the Krusader to kde4town - it and KMyMoney was requested several times via PMs.
Last edited by LuckyCyborg; 05-13-2023 at 02:20 AM.
I will be very happy if you manage to make a repository for this kde4town.
However, please bear in mind that one of fundamental ideas behind kde4town is to have a directories structure like the original KTown made by Mr. Hameleers. And the KTown had a kde directory for packages, and so on.
Also, please note that I have the intention to add also a i586 build for the "final release" for Slackware 15.0 - which rather depends on when @BrunoLafleur finishes the NetworkManager integration, which is heavily modified by him.
Finally, please note that I have the intention for this weekend to add the Krusader to kde4town - it and KMyMoney was requested several times via PMs.
I have kde/ in the blacklist file
and PRIORITY=( kde4 ) in slackpkgplus.conf
This way, slackware64/kde appears as [mask]
In fact, blacklist and PRIORITY in slackpkgplus.conf works pretty well, except for install-new command
slackpkg install-new always try to reinstall the whole kde/ set
I have kde/ in the blacklist file
and PRIORITY=( kde4 ) in slackpkgplus.conf
This way, slackware64/kde appears as [mask]
In fact, blacklist and PRIORITY in slackpkgplus.conf works pretty well, except for install-new command
slackpkg install-new always try to reinstall the whole kde/ set
Monsieur Marav, unfortunately I can't help you with any suggestions in this endeavor of yours because I have never used slackpkg.
For Internet bandwidth reasons, I have used always a local rsync mirror for Slackware, then from there propagation to various computers. Heck, until several years ago I have stayed in a 3G connection even at home. Only recently I have started to use 4G at home.
Last edited by LuckyCyborg; 05-13-2023 at 06:05 AM.
So, let me thank you very much for that hard work you made with BrunoLafleur
Except this trivial issue, I'm pretty sure it can be solved with a little patience, the KDE4town is working perfectly with a full installation through a repository
If @BrunoLafleur allows me, I would like to remind him of the maximum 4 thumbnails in the taskbar. It would be nice to have a maximum of 6 or 7 thumbnails.
With that about-distro, you seem to have solved it. Heartiest congratulations!
Last edited by ZhaoLin1457; 05-13-2023 at 06:36 AM.
The code bellow seems to give results most similar with what does the module present on KInfoCenter from Plasma5 .
My friend have also an explanation: some GL renderers (i.e. the NVIDIA blobs) may put a long information between parenthesis.
Code:
const QString Module::getGraphicsProcessor()
{
QGLWidget* glWidget = new QGLWidget;
QGLContext* glContext = (QGLContext *) glWidget->context();
glContext->makeCurrent();
QString ret = QString::fromUtf8(reinterpret_cast<const char *>(glGetString(GL_RENDERER)));
delete glWidget;
// Parse the result.
ret = fancyString(ret);
// It seems the renderer value may have excess information in parentheses ->
// strip that. Elide would probably be nicer, a bit meh with QWidgets though.
ret = ret.mid(0, ret.indexOf('('));
return ret.simplified();
}
The result of this update can be seen on the attached screenshot.
For me I prefer not to suppress informations. In some of my machines, that line suppress all the usefull information. There may be more than one group of parenthesis and the name of the chipset can be after the first parenthesis which may also contains only the (TM) mark.
But you can put the version you prefer. In pbslacks I prefer to not cut the string.
For me I prefer not to suppress informations. In some of my machines, that line suppress all the usefull information. There may be more than one group of parenthesis and the name of the chipset can be after the first parenthesis which may also contains only the (TM) mark.
But you can put the version you prefer. In pbslacks I prefer to not cut the string.
Well, in the latest getGraphicsProcessor() presented by me (at suggestion of my friend) the (TM) and (R) are already parsed by fancyString() before the cut is done. And was triple checked that a similar logic is done by the code from Plasma5.
Last edited by LuckyCyborg; 05-13-2023 at 07:04 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
