freedesktop.wayland-protocols-staging

// wayland-protocols, as a compositor would consume it.
//
// The packages ship the marshalling code wayland-scanner generates from
// upstream's XML. Three things can be wrong and none is a missing symbol:
//
//   1. THE HEADERS ARE THE PUBLIC INTERFACE. A consumer writes
//      `#include <xdg-shell-client-protocol.h>`, so the generated directory
//      has to be EXPOSED rather than build-private. This file compiling is the
//      first assertion, and freedesktop.wayland had exactly this bug once —
//      masked locally by a header the SubOS happened to carry.
//
//   2. THE INTERFACE TABLES MUST LINK. A header-only package sails past
//      compilation; `xdg_wm_base_interface` is a `wl_interface` OBJECT in the
//      generated .c, so reading it proves the .c files were compiled.
//
//   3. TWO TIERS MUST COMPOSE. stable and staging are separate packages
//      precisely so they can be used together; that they do is what this
//      member is for. (stable + unstable is the pair that cannot — 13 shared
//      symbols — which is upstream's semantics rather than a defect.)
//
// Nothing here connects: no compositor and no display.

// …