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.
Thanks, but I know it. And I use it since several years.
And you know what? Its Kate runs as Administrator. Can you believe it?
In fact, also the Kate from Plasma5 runs well as Windows super-user, even it refuse natively to run as root in a Linux operating system. Eric is kind to patch out this stupid behavior.
IF you want to try the latest and shiny Kate over Plasma5 within Windows. As Administrator.
BTW, if ever I will abandon Linux at all, probably I will go BSD. FreeBSD I think. You know how simple is to install all KDE4 and its dependencies on FreeBSD?
Code:
pkg install x11/kde4
Believe or not, has a shiny dependencies support and it is in direct line the grand son of the real UNIX.
The package dependencies aren't a scary RedHat invention, but they exists in UNIX, (Free)BSD and Solaris, which is UNIX as original you can get.
Last edited by Darth Vader; 06-23-2018 at 06:36 PM.
They do that only to hide their sloppy coding. Instead to fix bugs, is much simpler to do a recommendation, right?
For the sake of everyone's complete information, do you experience these same graphics bugs when running as a regular user?
(I'm not telling you to change your workflow, but I want to know if you are recommending not including Plasma 5 in Slackware because of a bug that only occurs when running in an unsupported way.)
Last edited by montagdude; 06-23-2018 at 06:35 PM.
For the sake of everyone's complete information, do you experience these graphics bugs when running as a regular user?
Yes, it have same behavior.
And when we talk about "regular user" I say a fresh created user, with no (suspect) files within its home. I create a new user after every upgrade of Plasma5, to test it clean.
Last edited by Darth Vader; 06-23-2018 at 06:39 PM.
From my experience, the graphic drivers works usually better as root, then if it is something wrong with them, there are better chances to manifest as a regular user.
Personally I am looking forward to the time when I check the changelog and I see Plasma 5 included. My own day to day use is with Fluxbox but even so I am a Slacker and I relish the idea of working on something like Plasma 5: bring it on .
Personally I am looking forward to the time when I check the changelog and I see Plasma 5 included. My own day to day use is with Fluxbox but even so I am a Slacker and I relish the idea of working on something like Plasma 5: bring it on .
Maybe you do not understand well the thread title; it is not "Do You Wish Plasma5 To Be Included in Slackware?"
Then, dear friend, why you say here wishes?
Last edited by Darth Vader; 06-23-2018 at 07:25 PM.
Thanks, but I know it. And I use it since several years.
And you know what? Its Kate runs as Administrator. Can you believe it?
In fact, also the Kate from Plasma5 runs well as Windows super-user, even it refuse natively to run as root in a Linux operating system. Eric is kind to patch out this stupid behavior.
IF you want to try the latest and shiny Kate over Plasma5 within Windows. As Administrator.
BTW, if ever I will abandon Linux at all, probably I will go BSD. FreeBSD I think. You know how simple is to install all KDE4 and its dependencies on FreeBSD?
Code:
pkg install x11/kde4
Believe or not, has a shiny dependencies support and it is in direct line the grand son of the real UNIX.
The package dependencies aren't a scary RedHat invention, but they exists in UNIX, (Free)BSD and Solaris, which is UNIX as original you can get.
Yeah not being able to use Kate in root seems like an odd design choice for a text editor.
Curiously, the KDE4 desktop depends on Qt5 and KDE Frameworks 5 — and it has for quite some time already, because the Oxygen icons are shared with KDE Frameworks, but primarily because FileLight was updated to the modern KDE Applications version some time ago (the KDE4 version had some serious bugs, although I can not remember what they were). Now that the names are cleaned up, we could consider giving KDE4 users the buggy version back.
FreeBSD ports aren't a rolling release. You can stay in a particular release and you will receive only bug-fixes, not breaking changes.
In other hand, they will not remove KDE4, practically you will have the ability to install either it or Plasma5.
I wish to be that ability also in Slackware, without studying 6 months the packages, to hunt down dependencies which theoretically no one knows.
Forget about Debian, RedHat or SuSE; even comparative with FreeBSD, or NetBSD and their PKGSRC, the Slackware way of packaging is terrible inefficient when it comes about customization, because of the lack of known package dependencies. I talk about at least knowledge like a long list, not specially about automated dependencies tracking. Because nobody pays you to study 6 months the dependencies who no one knows.
I know, I know, you shall install everything even in a head-less server who bring up a poor site.
BTW, they (the *BSD) have a core system, which is built at whole, with "make world", and you can rebuild that base system for real with that command; without a need to consult the gods about the build order.
And over that base system are the ports.
Last edited by Darth Vader; 06-23-2018 at 09:00 PM.
FreeBSD ports aren't a rolling release. You can stay in a particular release and you will receive only bug-fixes, not breaking changes.
In other hand, they will not remove KDE4, practically you will have the ability to install either it or Plasma5.
I wish to be that ability also in Slackware, without studying 6 months the packages, to hunt down dependencies which theoretically no one knows.
Forget about Debian, RedHat or SuSE; even comparative with FreeBSD, or NetBSD and their PKGSRC, the Slackware way of packaging is terrible inefficient when it comes about customization, because of the lack of known package dependencies. I talk about at least knowledge like a long list, not specially about automated dependencies tracking. Because nobody pays you to study 6 months the dependencies who no one knows.
I know, I know, you shall install everything even in a head-less server who bring up a poor site.
BTW, they (the *BSD) have a core system, which is built at whole, with "make world", and you can rebuild that base system for real with that command; without a need to consult the gods about the build order.
And over that base system are the ports.
I fail to understand why your not on freeBSD then -- it sounds like its already what you want.
I'm sure you know about Slackware's philosophy as you have been using Slackware for some time?
It's not how the distro should suit you, but it should be vice versa, you need to suit Slackware's way of doing things.
you can't really compare every distro out there as every distro have their own way and user base. If you think *BSD is good enough, you are free to try
Maybe you do not understand well the thread title; it is not "Do You Wish Plasma5 To Be Included in Slackware?"
Then, dear friend, why you say here wishes?
I understand the thread title well enough but my own attitude is slightly different and can be expressed perhaps a little more clearly with the following two points:
I am happy to leave wiser heads than mine to decide when is the best time to introduce Plasma 5 to Slackware -current. Soon? I hope so...
When it is introduced I will then happily run it around the block and participate in looking for any bugs or difficulties that arise, it is -current after all...
I try to avoid any sense of entitlement in such matters, Slackware has been kind to me over the years and my own contributions have been small. Perhaps your own contributions have allowed you to speak with more force?
Forget about Debian, RedHat or SuSE; even comparative with FreeBSD, or NetBSD and their PKGSRC, the Slackware way of packaging is terrible inefficient when it comes about customization, because of the lack of known package dependencies.
I've used all the distros you've mentioned. The Slackware way of packaging meets my needs; I find it elegant, logical, and very efficient. I'm a long-time BSD user who is moving back home to Slackware.
Each to his/her own, mate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.