Bug 261202 - x11-wm/river: add FLAVOR=nox11
Summary: x11-wm/river: add FLAVOR=nox11
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Jan Beich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-14 15:08 UTC by Oleh Vinichenko
Modified: 2022-01-22 13:07 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (jbeich)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleh Vinichenko 2022-01-14 15:08:58 UTC
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.
Comment 1 Oleh Vinichenko 2022-01-14 15:12:39 UTC
unlike with sway, river has no possibility to disable xwayland in it's configuration file, hence the request.
Comment 2 Jan Beich freebsd_committer 2022-01-22 09:35:50 UTC
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.
Comment 3 Oleh Vinichenko 2022-01-22 12:47:01 UTC
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.
Comment 4 Oleh Vinichenko 2022-01-22 13:07:08 UTC
but https://github.com/freebsd/freebsd-ports/commit/026ed2c6686a
is actually what i am looking for