Message-ID: <684539dc@news.ausics.net>
From: Computer Nerd Kev <not@telling.you.invalid>
Subject: Re: X.org fork, XLibre
Newsgroups: comp.windows.x
References: <101v47c$2c6k0$1@dont-email.me> <68438e89@news.ausics.net> <102376i$2c6k0$4@dont-email.me>
User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i686))
NNTP-Posting-Host: news.ausics.net
Date: 8 Jun 2025 17:21:00 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 26
X-Complaints: abuse@ausics.net
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!news.bbs.nz!news.ausics.net!not-for-mail

Alastair Hogge <agh@riseup.net> wrote:
> On Sat, 07 Jun 2025 10:57:46 +1000, Computer Nerd Kev wrote:
>> It'll be interesting to see whether many distros make packages for it
>> (including separate driver packages because the README notes that X.Org
>> drivers aren't binary compatible).
> 
> Am I missing something? From the README.md:
> 
>> Module ABIs have changed - drivers MUST be recompiled against this
>> Xserver verison, otherwise the Xserver can crash or not even start up
>> correctly.
>>
>> Most xorg drivers should run as-is (need recompile!), with some
>> exceptions. See .gitlab-ci.yml for the versions/branches built along
>> w/ Xlibre.

I read that as: the code for the drivers doesn't usually need to be
changed, but they need to be recompiled, so existing X.Org driver
packages won't work. Same as with Linux kernel drivers.

I suspect distro package maintainers won't consider it worth that
much effort given how many separate X packages they usually have.

-- 
__          __
#_ < |\| |< _#