Vote: making wayland=on default

Carmel NY carmel_ny at outlook.com
Wed Dec 20 11:44:11 UTC 2017


On Wed, 20 Dec 2017 09:20:20 +0000, Johannes Lundberg stated:

>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?

The normal scenario would be for FreeBSD to wait until other distros have
throughly vetted the application/protocol/device/other and then consider
adding it to the basic FreeBSD structure. Unfortunately, by that time the
target has moved on and FreeBSD is as all too often late to the party.

I am considering firing up an older PC I have laying around,install the
latest version of FreeBSD and then trying out a few application that are
presently not available or like "wayland" need some massaging. It all depends
if I can actually get some free time. Wayland does look promising though, I
hate "X".

-- 
Carmel


More information about the freebsd-ports mailing list