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

Doug Kirk dbkirk at gmail.com
Wed Dec 20 14:09:23 UTC 2017


+1

On Wed, Dec 20, 2017 at 5:56 AM 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).
> _______________________________________________
> freebsd-x11 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
>


More information about the freebsd-x11 mailing list