Bug#1101950: Please consider a configuration-only non-default package systemd-resolved-mdns

[Josh Triplett]

Package: systemd-resolved
Version: 257.4-9
Severity: wishlist
X-Debbugs-Cc: josh at joshtriplett.org

(Please note, this is a wishlist request, and low priority. It is not
meant to make additional work, and can wait until the current situation
calms down. Thank you for all your maintenance work.)

Since systemd-resolved -9 uses configuration to disable the mDNS
functionality by default (satisfying the requirement that the "default
installation" of systemd-resolved have mDNS disabled), would you
consider providing a *non-default* package systemd-resolved-mdns that
contains only a configuration snippet turning it back on (numbered to
come after the one in the base package turning it off)?

That way, users whose configurations do want to use mDNS with
systemd-resolved could depend on `systemd-resolved-mdns` and have it
Just Work.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.12.20-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-resolved depends on:
ii  dbus [default-dbus-system-bus]  1.16.2-2
ii  libc6                           2.41-6
ii  libssl3t64                      3.4.1-1
ii  libsystemd-shared               257.4-7
ii  systemd                         257.4-7

Versions of packages systemd-resolved recommends:
ii  libidn2-0          2.3.8-2
pn  libnss-myhostname  <none>
pn  libnss-resolve     <none>

Versions of packages systemd-resolved suggests:
ii  polkitd  126-2