@reaperx7, I should probably create those packages so that people won't have to modify or rebuild anything manually. So far, I've only uploaded xf86-input-libinput-xlibre
because it's a direct dependency. However, I used a suffix (xlibre
) instead of a prefix because it still uses the xorg
sources and just builds against xlibre
. There are existing repositories from xlibre
, but they all seem to be (equally?) inactive.
So, should my packages pull from the xorg
sources and use a suffix, or pull from the xlibre
sources and use a prefix? If the latter, what prefix would be appropriate instead of xf86
? Perhaps xlibref86
?
Pinned Comments
reaperx7 commented on 2025-06-14 00:26 (UTC) (edited on 2025-06-14 00:26 (UTC) by reaperx7)
Just a reminder for users, all xf86-input-<insert_name> and xf86-video-<insert-name> drivers have to be rebuilt against xlibre if you wish to use the standalone drivers for input and video needs.
Failure to rebuild these drivers will result in Xlibre refusing to load.
vitaliikuzhdin commented on 2025-06-12 15:42 (UTC) (edited on 2025-06-12 18:37 (UTC) by vitaliikuzhdin)
If you're having trouble installing
xlibre-server-git
due to circular dependencies, follow this procedure:Similarly, to revert:
This is an unfortunate reality of building AUR packages with circular dependencies from source. I don’t like this solution, but at least it's a solution.
I'm also considering an alternative approach: having
xlibre-server
providexlibre-server-bootstrap
, so that packages needing to build againstxlibre-server
can listxlibre-server-bootstrap
as amakedepends
instead. If you're knowledgeable about this or have a good argument for or against it, I’d appreciate your input.