x11-wm/river port currently has X11 option default enabled, which then has gives xwayland automatically enabled at compilation time and resulting pkg uses Xwayland at runtime. This might be suboptimal to users, who use pure wayland setups.
unlike with sway, river has no possibility to disable xwayland in it's configuration file, hence the request.
Can you define a "pure Wayland setup"? Lots of packages river indirectly depends on have X11 enabled by default (including wlroots), so river@nox11 won't be pure. Without provides/requires (aka variable dependencies or package alternatives) getting rid of X11 requires touching unrelated ports e.g., https://github.com/freebsd/freebsd-ports/commit/026ed2c6686a (haven't rebased or adapted to river yet) If you just want to prevent all apps from using Xwayland run "unset DISPLAY" after starting river or add "env -u DISPLAY ..." to "riverctl ... spawn". Maybe also remove the socket file under /tmp/.X11-unix/ in case apps set DISPLAY=:0 themselves as a fallback. Note, @nox is only used by emacs where it's a wordplay on dark mode due to default console theme using white font on black background.
in my terminology, it is when Xwayland is disabled. I suspected such complications, so i guess this request can be closed as no-go :) i missed the fact that there is no interdependent X11=off for all dependencies for such flavor.
but https://github.com/freebsd/freebsd-ports/commit/026ed2c6686a is actually what i am looking for