Package: cage
Version: 0.2.0-2
Severity: normal

Dear Maintainer,

While xwayland must be enabled at compile time, it is not a requirement at 
runtime.
I have tested this in a VM by force installing the cage package and running 
foot with it.
It emits an warning about the Xwayland executable not being present but 
continues normally.

I posit that xwayland should at least be moved to Recommends.
It could potentially be removed from dependencies altogether, as is the case 
with sway.

-- System Information:
Debian Release: 13.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.48+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cage depends on:
ii  libc6               2.41-12
ii  libwayland-server0  1.23.1-3
ii  libwlroots-0.18     0.18.2-3
ii  libxkbcommon0       1.7.0-2
ii  xwayland            2:24.1.6-1

cage recommends no packages.

cage suggests no packages.

-- no debconf information

Reply via email to