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

[John Scott]

This is just a drive-by comment: making a new binary package just for a configuration file snippet doesn't seem like a great tool for the job. Usually a debconf option (perhaps set at low, not-shown-by-default priority) is the tool of choice for scenarios such as this. This would make it easy for sysadmins to have this set by default via installer preseeding or your preferred choice of Debconf backend, and also make the option discoverable using standard system tools. For gurus running Debconf on low-priority mode or using the expert installer, this will also allow including a blurb about why this *isn't* the default and allow making an informed decision.

Downstream customization issues such as this are just what Debconf was made for. Using that would be preferable to making a new binary package with just a single text file, say.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20250930/0f67d61c/attachment.sig>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4290 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20250930/0f67d61c/attachment.p7s>