Date: Wed, 20 Dec 2017 10:31:44 -0800 From: Pete Wright <pete@nomadlogic.org> To: Johannes Lundberg <johalun0@gmail.com>, freebsd-x11@freebsd.org Subject: Re: Vote: making wayland=on default (also posted to ports@) Message-ID: <cb7323f5-f2dc-b19b-c1dc-271c82e532e1@nomadlogic.org> In-Reply-To: <CAECmPwsN15WxSuXynto=RxTyztQdUjU5vaR6Y%2BCEkqDNW3_5Rg@mail.gmail.com> References: <CAECmPwsN15WxSuXynto=RxTyztQdUjU5vaR6Y%2BCEkqDNW3_5Rg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/20/2017 03:55, 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? > +1 Not having to track local diffs to enable wayland in gtk30 and friends would be really helpful for me to test/dog food things. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb7323f5-f2dc-b19b-c1dc-271c82e532e1>