How to update Wayland_jll?

[eschnett]

I tried building a new version of Wayland_jll because I encountered a deep rabbit hole and both HarfBuzz and Wayland were at the end of it.

I think Wayland_jll of version X has Wayland_jll of version X as host build dependency. That's weird – how has this ever worked? I tried building Wayland 1.23.1, and it requested wayland-scanner version 1.23.1 to be present, and this executable is provided by the very package I'm trying to build.

[barche]

I believe #10876 will solve this. The mechanism used is similar to what happens in Qt6, where the build on x86_64-linux-musl is used to supply tools for the cross-compiled builds. In this case, it is solvable by just always building these host tools, so the HostBuildDependency can be removed. This is the preferred way, because otherwise an in-between release with only the host build is required, and this can cause breakage while the target builds are under construction.

I am also closing PR #10813 in favor of this.

[eschnett]

If you name the host tools package WaylandScanner and the actual package Wayland then the dependency chain is clear and cannot cause breakage.

However, your approach is simpler because there is only a single package. The disadvantage of your approach is that the host tools are built many times, and their dependencies need to be installed. In any way, your approach is working fine.