Package Details: xlibre-server-xnest-git 25.0.0.4.r5.7437ce8e3-1

Git Clone URL: https://aur.archlinux.org/xlibre-server-git.git (read-only, click to copy)
Package Base: xlibre-server-git
Description: A nested XLibre server that runs as an X application
Upstream URL: https://github.com/x11libre/xserver
Licenses: MIT, ISC, X11, ICU, BSD-3-Clause, LicenseRef-Adobe-Display-PostScript, LicenseRef-DEC-3-Clause, HPND, LicenseRef-HPND-sell-MIT-disclaimer-xserver, HPND-sell-variant, MIT-open-group, NTP, SGI-B-2.0, SMLNJ, X11-distribute-modifications-variant
Groups: xlibre-git
Conflicts: xlibre-server-xnest, xorg-server-xnest
Provides: xlibre-server-xnest
Submitter: vitaliikuzhdin
Maintainer: vitaliikuzhdin
Last Packager: vitaliikuzhdin
Votes: 29
Popularity: 19.67
First Submitted: 2025-06-09 19:09 (UTC)
Last Updated: 2025-07-07 14:01 (UTC)

Pinned Comments

vitaliikuzhdin commented on 2025-06-23 22:16 (UTC) (edited on 2025-07-01 15:45 (UTC) by vitaliikuzhdin)

reserved

vitaliikuzhdin commented on 2025-06-12 15:42 (UTC) (edited on 2025-07-08 14:32 (UTC) by vitaliikuzhdin)

Installation instructions:

  1. Prepare a non-X session. If you still want a GUI session, (temporarily) opt for another backend, such as Wayland. If you're fine with using the terminal, perform everything from a fresh TTY. This is an unfortunate requirement because installing XLibre requires removing Xorg, which obviously breaks the X session.

  2. Install xlibre-server-bootstrap. This is a bootstrap package and will not provide a working X session, so be sure to follow the next steps!

  3. When prompted to install xlibre-server-bootstrap, pacman will report a few conflicts, namely with xorg-*, xf86-*, and packages that depend or makedepend on Xorg components. Agree to remove those (but be careful, these are likely important packages) and make note of their names.

  4. Install xlibre-input-libinput. Again, expect similar conflicts.

  5. Install xlibre-server. When prompted, agree to replace xlibre-server-bootstrap.

  6. For every xorg-* and xf86-* package you previously removed, install an xlibre-* counterpart. I’ve uploaded all the xlibre-drivers counterparts for the xorg-drivers group from extra, but I haven’t touched the AUR-only drivers yet. I’m considering adding them once I’ve researched further. In the meantime, feel free to request a specific one.

  7. For every other package you previously removed, you’ll need to manually modify the PKGBUILD to update provides, conflicts, and ABI versions, and then recompile them. In theory, many of the packages removed due to requiring xorg-server don’t actually need recompilation and should depend on x-server instead, but good luck getting Arch/AUR maintainers to fix those. You may also upload your modified PKGBUILDs to the AUR with a changed pkgname and pkgdesc. I suggest naming them $original_pkgname-xlibre and appending something like (built against XLibre) to the pkgdesc.

Important notes

  1. If you fail to fully complete a step, do not continue, it will not magically fix itself. Better to exit early than waste your time.

  2. Installing and using this as a daily driver is a hassle. If you’re unsure of your skills, don’t do it, and definitely don’t blame anyone else (including the project authors or me) for your mistakes. And don't be like this guy: https://files.catbox.moe/yqoe5e.png

  3. Do not report packaging or installation issues to the upstream. They won’t be able to help, even if they wanted to, since we are not affiliated in any way. If you’re unsure who to report your issue to, describe the situation here and we’ll decide together whether it’s a task for me or for upstream.

Latest Comments

vitaliikuzhdin commented on 2025-06-25 15:18 (UTC)

@guiodic, I don't see why not. Are you asking because it's a VCS package or because it's an X.Org package? If it's the former, it's hard to say in advance whether everything will work. If it's the latter, there doesn't appear to be an XLibre counterpart (or am I missing something?).

guiodic commented on 2025-06-25 15:12 (UTC)

is xorgproto-git still valid for xlibre?

vitaliikuzhdin commented on 2025-06-23 22:16 (UTC) (edited on 2025-07-01 15:45 (UTC) by vitaliikuzhdin)

reserved

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-07-08 14:32 (UTC) by vitaliikuzhdin)

Installation instructions:

  1. Prepare a non-X session. If you still want a GUI session, (temporarily) opt for another backend, such as Wayland. If you're fine with using the terminal, perform everything from a fresh TTY. This is an unfortunate requirement because installing XLibre requires removing Xorg, which obviously breaks the X session.

  2. Install xlibre-server-bootstrap. This is a bootstrap package and will not provide a working X session, so be sure to follow the next steps!

  3. When prompted to install xlibre-server-bootstrap, pacman will report a few conflicts, namely with xorg-*, xf86-*, and packages that depend or makedepend on Xorg components. Agree to remove those (but be careful, these are likely important packages) and make note of their names.

  4. Install xlibre-input-libinput. Again, expect similar conflicts.

  5. Install xlibre-server. When prompted, agree to replace xlibre-server-bootstrap.

  6. For every xorg-* and xf86-* package you previously removed, install an xlibre-* counterpart. I’ve uploaded all the xlibre-drivers counterparts for the xorg-drivers group from extra, but I haven’t touched the AUR-only drivers yet. I’m considering adding them once I’ve researched further. In the meantime, feel free to request a specific one.

  7. For every other package you previously removed, you’ll need to manually modify the PKGBUILD to update provides, conflicts, and ABI versions, and then recompile them. In theory, many of the packages removed due to requiring xorg-server don’t actually need recompilation and should depend on x-server instead, but good luck getting Arch/AUR maintainers to fix those. You may also upload your modified PKGBUILDs to the AUR with a changed pkgname and pkgdesc. I suggest naming them $original_pkgname-xlibre and appending something like (built against XLibre) to the pkgdesc.

Important notes

  1. If you fail to fully complete a step, do not continue, it will not magically fix itself. Better to exit early than waste your time.

  2. Installing and using this as a daily driver is a hassle. If you’re unsure of your skills, don’t do it, and definitely don’t blame anyone else (including the project authors or me) for your mistakes. And don't be like this guy: https://files.catbox.moe/yqoe5e.png

  3. Do not report packaging or installation issues to the upstream. They won’t be able to help, even if they wanted to, since we are not affiliated in any way. If you’re unsure who to report your issue to, describe the situation here and we’ll decide together whether it’s a task for me or for upstream.