You are not logged in.
Is there a technical reason for the glfw-wayland/glfw-x11 split? All the other distros just seem to have a single glfw package, which seems far more practical in that you don't find yourself locked into only choosing one type of graphical sessions, and that there isn't issues with packages compiled exclusively for either without an underlying technical reason (such as librealsense in AUR).
Please correct me if I'm wrong, and thank you for your time.
Last edited by Svanto (2021-06-26 15:00:01)
Offline
The provides & conflicts in those packages suggest they can't coexist .
$ pkgfile libglfw.so.3.3
community/glfw-wayland
community/glfw-x11
$
Both provide the same library, but one is linked to libwayland-client.so.0 and the other to libX11.so.6 .
As for other distros :
debian stable does the same as archlinux :
[1] is for X11, [2] is for wayland .
[1] https://packages.debian.org/buster/libglfw3]libglfw3 for X11
[2] https://packages.debian.org/buster/libglfw3-wayland
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Understood, sounds like an unfortunate choice on glfw's part then.
Thank you for correcting my misimpression.
Offline
You're welcome, please prepend [Solved] to the thread title .
(edit first post, you may have to shorten the exisitng title to add solved)
Last edited by Lone_Wolf (2021-06-26 14:00:40)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline