Package Details: xlibre-server-xvfb-git 21.1.13.r3009.942b0e96c-1

Git Clone URL: https://aur.archlinux.org/xlibre-server-git.git (read-only, click to copy)
Package Base: xlibre-server-git
Description: Virtual framebuffer XLibre server
Upstream URL: https://github.com/x11libre/xserver
Licenses: MIT, GPL-2.0-only
Groups: xlibre-git
Conflicts: xlibre-server-xvfb, xorg-server-xvfb
Provides: xlibre-server-xvfb, xorg-server-xvfb
Submitter: vitaliikuzhdin
Maintainer: vitaliikuzhdin
Last Packager: vitaliikuzhdin
Votes: 12
Popularity: 11.27
First Submitted: 2025-06-09 19:09 (UTC)
Last Updated: 2025-06-12 15:38 (UTC)

Required by (299)

Sources (3)

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:

yay -S xlibre-server-bootstrap-git
yay -S xf86-input-libinput-xlibre
yay -S xlibre-server-git

Similarly, to revert:

pacman -S xorg-server xf86-input-libinput

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 provide xlibre-server-bootstrap, so that packages needing to build against xlibre-server can list xlibre-server-bootstrap as a makedepends instead. If you're knowledgeable about this or have a good argument for or against it, I’d appreciate your input.

Latest Comments

reaperx7 commented on 2025-06-14 21:21 (UTC)

I would just use the suffix *-xlibre for now. The xlibre prefix might seem misleading to some people.

vitaliikuzhdin commented on 2025-06-14 08:48 (UTC)

@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?

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:

yay -S xlibre-server-bootstrap-git
yay -S xf86-input-libinput-xlibre
yay -S xlibre-server-git

Similarly, to revert:

pacman -S xorg-server xf86-input-libinput

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 provide xlibre-server-bootstrap, so that packages needing to build against xlibre-server can list xlibre-server-bootstrap as a makedepends instead. If you're knowledgeable about this or have a good argument for or against it, I’d appreciate your input.