Zig 0.16

[tranzystorekk]

Testing the changes

• I tested the changes in this PR: YES|briefly|NO

[jonpikum]

Please correct anything I might not have understood about this topic, but per the discussion in #60034...
It looks like river 0.4 is a pretty major break, removing both riverctl and rivertile (the actual WM part).
I think this means that any user of river will go from having a working DE with 0.3 to.. well.. not, with 0.4.
No key-binds, no way to open a new terminal window, maybe worse? IDK.

The blog post discussing the changes to river links to another page with a list of WMs that work with the new protocol.
It looks like river provides an example tinyrwm and states that the C example is canonical - however, there are no tagged releases.
Maybe this PR should could include at least one of these so that users have an option to get started with, rather than needing to compile one of these themselves? (potentially from a non-working environment)

Edit: links, verbiage, clarify tinyrwm state

[tranzystorekk]

The nature of a rolling distro means this will be a breaking change with an INSTALL.msg announcement displayed during update, but you raise some valid points:

• we should wait for river-classic to release a zig 0.16 update to be able to provide it as a package
• packaging at least one modern river wm seems like a prudent idea

[classabbyamp]

re: river:

I've packaged and tested river with rrwm, but I don't think I'll be using it at this time. My recommendation is:

• river WMs should depend on river>=4.4.0
• river WMs should provides="river-wm-0_1"
• an install message should mention installing a WM, with a link to the river wiki's list of WMs, and maybe saying you can find packaged WMs with xbps-query -Rp provides -s river-wm

[al20ov]

Ghostty doesn't build either (neither the old 1.1.3 nor 1.3.1) but they're working on updating everything to zig 0.16 right now: ghostty-org/ghostty#12388

[Nizarjh]

i am going to push ly if u push zig. So good luck