Closed Person1873 closed 11 months ago
This is not going to be fixed because hyprland has made it clear that they will not support system wide wlroots. This option is there for developers who want to work on wayland/wlroots codebase.
This is not going to be fixed because hyprland has made it clear that they will not support system wide wlroots. This option is there for developers who want to work on wayland/wlroots codebase.
ok, so if upstream does not support this option, then why do we include it at all in our ebuild? I would gently suggest that those developers are able to clone their own versions of the codebase and try these unsupported options outside of the portage ecosystem?
Allowing multiple configurations isn't a problem. Just don't use the option, I don't see a big problem for having it available. Plus just because upstream doesn't support it doesn't mean we have to agree with that decision, using a shared library means we don't have to keep thinking about embedded copy vulnerabilities. I've disabled it by default - https://github.com/bsd-ac/wayland-desktop/commit/0577332ef4d2c418902f50ae88b74e9ef7a26802
hyprland is in gentoo now
Hyprland fails to build if you set the USE flag "system-wlroots"
The package needs to depend on gui-libs/wlroots when this is set. please note that setting "gui-wm/hyprland -system-wlroots" in /etc/portage/package.use/hyprland allows it to use hyprlands built in wlroots