Wow, I thought they would have done this long time ago.
Even Ubuntu have done this before.
In 13.04 Raring Ringtail, the Wayland backend in GTK+ is compiled in.
I expected Arch to do this before Ubuntu.
I am disappointed in Arch.
Phoronix: Arch Linux Enables Wayland GTK+
For those Arch Linux users looking to play with Wayland/Weston, the GTK+ package available within the distribution now enables support for the Wayland back-end...
http://www.phoronix.com/vr.php?view=MTMzMTA
Wow, I thought they would have done this long time ago.
Even Ubuntu have done this before.
In 13.04 Raring Ringtail, the Wayland backend in GTK+ is compiled in.
I expected Arch to do this before Ubuntu.
I am disappointed in Arch.
Remember, Arch doesnt play with build flags. If upstream didnt have this enabled by default at build time, Arch probably wouldnt have. Its very rare that Arch ships a non-default configuration by default. (the other exception to this was to Mesa for one of the patented items)
I think they don't have a problem enabling build flags for features.
The problem is that gtk is in the [extra] repository and I believe wayland has been in the [community] repository and they don't enable flags that require software from another repository I think. Now wayland is in [extra] so they could do it. Another concern is that people may use gtk3 but don't need wayland, should they have to install it? Messy solution: Provide gtk3-wayland alongside gtk3. Not it requires you to install wayland when installing gtk3. It's only 580 kilyobyte but still, some people potentially care... At least wayland only depends on libffi and expat.
Gnumeric and galculator work under Weston.(gnumeric caused a segfault in something, but continued running regardless)
Now I can't wait for Gtk to have decorations support and applications to stop using X specific libraries.![]()