使用 Homebrew, apk, MacPorts, Nix, pacman, apt, dnf, zypper 安装 wayland

项目链接

• 主页
• 仓库
• 上游文档
• 软件包管理器页面

命令和别名

• wayland-scanner

项目历史

The official Wayland site describes Wayland as a replacement for the X11 protocol and architecture, intended to be easier to develop, extend, and maintain. Its architecture page explains the core shift: under X, the X server sits between clients, compositors, input, and rendering; under Wayland, the compositor receives input, manages the scene, and accepts client buffers directly.

Wayland and Weston reached 1.0.0 on 2012-10-22, a release the project says marked stable protocol and client-side APIs. The core stack later split into a family of release streams: Wayland for the protocol and C libraries, Weston as a reference compositor, wayland-protocols for shared extensions, and wayland-utils for inspection/debugging.

The first wayland-protocols 1.0 release appeared on 2015-11-24. That extension repository became the place where desktop and application protocols could be reviewed and staged, including stable, staging, deprecated, and legacy unstable protocol phases.

采用历史

Wayland adoption was gradual because it replaces a core desktop substrate and depends on graphics drivers, compositors, toolkits, screen capture paths, remote desktop flows, and XWayland compatibility. GNOME's 3.22 release notes in 2016 framed Wayland as the next-generation display/input technology for GNU/Linux, and Fedora's Fedora 25 change moved GNOME's display manager/session default to Wayland with Xorg fallback.

KDE followed a slower route through Plasma and KWin. Fedora's Plasma Wayland-by-default change for Fedora 34 stated that KDE Plasma Desktop would use Wayland while X applications continued through XWayland, and KDE's Plasma 6 mega-release in 2024 made Wayland the preferred modern Plasma path.

使用方式

For application and compositor developers, the Homebrew-visible tool is `wayland-scanner`, which turns XML protocol descriptions into C headers and glue code. Runtime use is usually indirect: a toolkit such as GTK, Qt, SDL, GLFW, or a compositor such as GNOME Shell, KWin, Sway, Weston, or gamescope links against libwayland and speaks the protocol.

For users and packagers, Wayland is not a command-line application so much as a foundational runtime component. It is installed because compositors, toolkits, screen portals, XWayland, and protocol extension packages need a shared ABI and protocol generator.

为什么软件包爱好者会关心

Wayland is package-nerd significant because it changed Linux desktop dependency graphs. Installing a graphical application stack now often pulls in libwayland-client, libwayland-server, wayland-protocols, xdg-desktop-portal, and XWayland rather than assuming an Xorg-only world.

It also turned protocol XML into a build-time artifact: packages commonly use `wayland-scanner` to generate source from protocol definitions, which makes the small `wayland` package important even on systems that never launch Weston.

时间线

• 2012-10-22: Wayland and Weston 1.0.0 are released, marking stable protocol and client-side APIs.
• 2015-11-24: wayland-protocols 1.0 is released.
• 2016-09-20: Wayland and Weston 1.12 are released around the Fedora 25/GNOME Wayland default transition period.
• 2018-04-09: Wayland 1.15 and Weston 4.0 are released.
• 2024-02-28: KDE Plasma 6 ships as part of KDE's MegaRelease 6 with Wayland as the modern default path.
• 2026-03-19: Wayland 1.25.0 is released.

Related projects

• Closely related projects include Weston, wayland-protocols, wayland-utils, XWayland, Mesa, Linux DRM/KMS, GNOME Shell/Mutter, KDE KWin/Plasma, wlroots, Sway, xdg-desktop-portal, GTK, and Qt.

来源

• https://fedoraproject.org/wiki/Changes/WaylandByDefault
• https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPlasma
• https://kde.org/announcements/megarelease/6/
• https://release.gnome.org/3-22/
• https://wayland.freedesktop.org/
• https://wayland.freedesktop.org/architecture.html
• https://wayland.freedesktop.org/docs/html/
• https://wayland.freedesktop.org/releases.html