Date: Wed, 20 Dec 2017 13:31:06 +0000 From: Johannes Lundberg <johalun0@gmail.com> To: FreeBSD <freebsd-ports@freebsd.org> Cc: antranigv <antranig@vartanian.am> Subject: Re: Vote: making wayland=on default Message-ID: <CAECmPwt8_Dks%2Bo_DerEouLWMAV21EccNi_viUeq-Bri5-YUgtw@mail.gmail.com> In-Reply-To: <0ecaf46d-e7bc-04cd-212a-bc0606cc7eec@evnbug.org> References: <CAECmPwtgtxJ-Nv6_LWoZC14UQ7TRZR%2B6Bg=1TK5=FuKz78hFNQ@mail.gmail.com> <0ecaf46d-e7bc-04cd-212a-bc0606cc7eec@evnbug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 20, 2017 at 1:13 PM, antranigv <antranig@vartanian.am> wrote: > Hi! > > Trying to understand the changes that would be made by making wayland=on > by default. > > I see a lot of people moving to Wayland from X, but if we do wayland=on, > what will this mean to Xorg people? from the first thing I got is larger > binaries for gtk and Qt. anything else that will happen? please fill me > in, I'd love to vote wayland=on by default if people think it's the > future, but without hurting people who still use and like Xorg. > Hi! Yes, libraries that are common for X and Wayland like mesa-libs, qt5 and gtk30 will get a bit bigger in order to enable Wayland. This is completely transparent to X users and does not affect X-related stuff in anyway. Using Wayland compositors like x11-wm/sway or x11-wm/weston is still completely optional and can they can co-exist with any X server and X11 window manager. Simply run "startx" if you wanna run X or "weston-launch" if you wanna run weston. Any X client should run fine in Weston (requires the pkg "xwayland"), however the opposite is not true. > Thanks in advance, > > antranigv > https://antranigv.am/ | PGP Key ID : 0xDAB81456 > /* do one thing and do it well */ > > On 12/20/2017 01:20 PM, Johannes Lundberg wrote: >> Hi >> >> I want to suggest that we enable wayland by default. In current state >> having some parts of wayland in ports is basically useless the >> end-users themselves re-build gtk30 and mesa-libs with wayland >> enabled. >> >> libwayland-egl.so from mesa-libs and the extra libraries and headers >> from gtk30 adds like a few KB, a drop in the ocean compared to xorg >> packages. (might be something more that I missed) >> >> Personally I see no reason not to make it default on, even with >> flavors coming up. For any Desktop user (as well as embedded devices >> like IVI-systems and whatnot), Wayland is the future. There's no >> escaping that. >> >> Wayland has been quite usable on FreeBSD for over a year now but >> access to it is limited due to the extra efforts required to use it. >> >> If we are to compare with the other guys, several Linux distros are >> already switching to wayland-based compositors as default window >> server. >> >> What do you think? >> >> >> /Johannes >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAECmPwt8_Dks%2Bo_DerEouLWMAV21EccNi_viUeq-Bri5-YUgtw>