[SOLVED] wayland required even with -wayland flag

[robinelvin]

This may be more of a portage question but could someone explain why emerge wants to use wayland for a few package upgrades when I have specifically said not to enable it in my make.conf?

e.g.

Code: Select all

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by app-office/libreoffice-25.2.5.2::gentoo[gtk3]
# required by @selected
# required by @world (argument)
>=x11-libs/gtk+-3.24.49-r1 wayland
# required by app-office/libreoffice-25.2.5.2::gentoo[gtk4]
# required by @selected
# required by @world (argument)
>=gui-libs/gtk-4.16.13 wayland
# required by gui-libs/gtk-4.16.13::gentoo[vulkan]
# required by app-office/libreoffice-25.2.5.2::gentoo[gtk4]
# required by @selected
# required by @world (argument)
>=media-libs/vulkan-loader-1.4.321.0 wayland
# required by x11-libs/gtk+-3.24.49-r1::gentoo[wayland]
# required by xfce-extra/xfce4-screensaver-4.20.0-r1::gentoo
# required by xfce-base/xfce4-session-4.20.2::gentoo[xscreensaver]
# required by xfce-base/xfce4-meta-4.20::gentoo
# required by @selected
# required by @world (argument)
>=media-libs/mesa-25.1.7 wayland

I really don't want or need wayland on my system so I don't understand why it now seems a requirement.

[grknight]

Duplicate of Why do gtk+ and mesa now require wayland?

[NeddySeagoon]

robinelvin,

USE=-wayland disables wayland where its optional.
Some things will not build without wayland support and force their dependencies to support it too.

Wayland is a protocol, not an entire GUI, so you will have wayland protoco support.
If you wanted a wayland compatible GUI, you start with a conpositor, then add wayland applications to make use of the compositor.
In short, wayland does not add much.

To minimise the overhead where you don't want wayland, it can be enabled on a per package basis.

As wayland support grows, so will this list.