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.
Will you be removing anything Wayland-related from ktown/latest that Pat has added to -current? The wayland-protocols-1.18-noarch-1 package would seem to be a good candidate for removal. I ask, obviously, because I use slackpkg+ with ktown being given priority.
If Wayland is used purely as a backend for X, it's not a problem (I think even 3d acceleration can be forwarded). On the other hand, I suspect we would be losing essentially everything that is not gtk or qt, because Wayland demands way too much from a toolkit, much more than non-bloated toolkits, such as Motif or fltk provide.
Wayland in Plasma5 requires the presence on your computer of a program implementing the login1 D-BUS APi.
As I suspected. Just backdoor. You cannot slice it forever and through its parts all over the system. What's difference to have it in one piece or in parts? It only sounds better. Forcing wayland is another step in that process. Better be honest with us.
Oh good lord. Nobody forces anything on anyone in Slackware. You want to use pulse? Use pulse. You want to use ALSA and no pulse? There are solutions for that. Hell, people are even using systemd with Slackware, for some reason known only to those who use it, and people are still maintaining GNOME, when that was dropped like 10 years ago in the distro. There's no indication that xorg-server is being removed for xorg-server-wayland, and it would really, really surprise me if they did. And if they did, start looking for pods, because aliens got Pat.
Yes, but if others distributions accept wayland as their default Xorg replacement what KDE developers may start to think? I think that they may start to think that time has come.
Yes, but if others distributions accept wayland as their default Xorg replacement what KDE developers may start to think? I think that they may start to think that time has come.
Has any distribution completely replaced X with Wayland, even as a test? Anyway... we added Wayland to get ahead of the curve, so to speak, especially since Plasma 5 can possibly make some use of it. It's not too big, and might be fun to play with - we'll see. Meanwhile don't worry about X becoming an endangered species around here. It will continue to be the main priority for the long foreseeable future.
As I suspected. Just backdoor. You cannot slice it forever and through its parts all over the system. What's difference to have it in one piece or in parts? It only sounds better. Forcing wayland is another step in that process. Better be honest with us.
Were you drunk or high when you wrote this>? You think Slackware is adding a back door? You state that Pat is not honest about his intentions? Better sober up or find another dummy to hit with your stick.
Will you be removing anything Wayland-related from ktown/latest that Pat has added to -current? The wayland-protocols-1.18-noarch-1 package would seem to be a good candidate for removal. I ask, obviously, because I use slackpkg+ with ktown being given priority.
I maintain my repositories in my own free time, which is quite limited. I will get to that cleanup, sure, but I can not always keep up with or anticipate Patrick's updates in the official distro package tree.
I expect that people are capable of managing their own systems in the meantime.
Distributions in general can do very little in deciding where to go. Distributions adopt what is developed. Since RedHat seems quite determined to ditch X eventually, and they provide the main pool of developers, theyv decide.
Distributions in general can do very little in deciding where to go. Distributions adopt what is developed. Since RedHat seems quite determined to ditch X eventually, and they provide the main pool of developers, theyv decide.
Nah, I didn't mean RedHat as a distribution (I would have said RHEL or Fedora), but rather as a company. If people want Slackware (or indeed any other distribution) to be able to use X11 without Wayland, they need to make sure that X11 is usable without Wayland (as without xwayland) after the major donors to X.org leave (and perhaps refocus on Wayland). It is not the distributions who matter in this question. The distributions package everything, as long as it works.
Nah, I didn't mean RedHat as a distribution (I would have said RHEL or Fedora), but rather as a company. If people want Slackware (or indeed any other distribution) to be able to use X11 without Wayland, they need to make sure that X11 is usable without Wayland (as without xwayland) after the major donors to X.org leave (and perhaps refocus on Wayland). It is not the distributions who matter in this question. The distributions package everything, as long as it works.
You are making all sorts of unfounded assumptions here. I call that FUD.
And X does not depend on Wayland. X clients can run in a Wayland session, seamlessly. So even if there is a future where Wayland is the default technology adopted by software programmers, all your X based applications will still run and you will be able to use them as before.
And X is too widely established to just fade away into the dark. As stated in the Wayland documentation - Wayland protocol was not developed with the graphical desktop environment in mind. Everything is still possible.
Redhat has its motives and drives progress in the Linux open source ecosystem, but they are not the only one, and they are not the ruler of this universe.
Indeed, and sorry if I sounded a bit harsh. I just want to prevent the spread of incorrect facts and unfounded assumptions about what (a) Wayland is going to mean for Linux and (2) what Slackware is going to do with Wayland.
XWayland is the glue code which allows a XWindow client to be embedded and managed by a Wayland compositor (window manager). It is part of the X.Org code but note that XWayland is not required/used if you run X in the absense of Wayland.
What you showed there (Red Hat contributing to the XWayland code) shows that Red Hat not just cares about getting Wayland accepted but also to make it work together with X.Org.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
