Vote: making wayland=on default (also posted to ports@)

[Gary Jennejohn]

On Wed, 20 Dec 2017 11:55:58 +0000
Johannes Lundberg <johalun0 at gmail.com> 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?
> 
> 
> Edit: This does not break or modify anything existing. It does not
> force you to do anything different. It simply adds a couple of
> libraries that you won't use unless you run wayland stuff (if you
> install gtk30 and mesa-libs).
>

Can you guarantee this?  I seem to have mesa-libs stuff installed
even though I use the nvidia-driver.  May be that pkg just
installed mesa-libs as a dependency for some other package.

I'm using the AMD Ryzen which has no on-board graphics, so I'm
happily using my NVIDIA GPU and have absolutely no desire to
change because someone enables wayland by default.

-- 
Gary Jennejohn