Xorg-server release candidate drops autotools, disables byte-swapped clients by default

The shift from autotools to Meson as the sole build system removes decades-old tooling dependencies. Teams that package Xorg-server for distributions or embed it in appliances will need to rewrite build scripts, test cross-compilation paths, and update CI pipelines. Meson’s faster build times may offset migration costs, but the change is mandatory, no fallback to autotools remains.

Security defaults have tightened: byte-swapped clients and font-server connections are now disabled unless explicitly enabled in xorg.conf. This breaks compatibility with legacy applications that rely on these features without configuration changes. Engineers must audit their stacks for dependencies on byte-swapped clients, particularly in environments where network transparency is used across endianness boundaries.

Log file management changes: Xorg now writes logs to $XDG_STATE_HOME/xorg by default, moving away from root-owned directories. This aligns with modern desktop standards but may disrupt log aggregation tools or troubleshooting workflows that expect logs in /var/log. Teams will need to update log rotation rules and monitoring agents to track the new location.

The release candidate introduces platform-specific updates, including DRM support for BSD and multiple CRTC support in Xvfb. These changes expand testing capabilities but may require adjustments to virtual display configurations. The recommendation to build against libpciaccess 0.19 adds another dependency, as some bug fixes rely on its new API, which is only detected at build time.