> So, if I read your request correctly, moving avahi-daemon from depends
> to recommends would be satisfactory?
You'd need to move all three of avahi-daemon, avahi-autoipd, and
libnss-mdns, because they work in concert. A convenient method may be
to create a recommends dependency on a separate "avahi-desktop"
package that depends on all three.
It's not an optimal solution, but it is a workable one. As I have
written at length on many occasions, avahi is insecure and unreliable
for users, imposes an unnecessary burden on the Internet at large,
and should be deprecated (certainly not installed by default). A
"suggests" dependency would require a conscious decision to activate
and is much preferred. However, moving "los tres diablos" to
recommends would at least allow a user to purge them and still
preserve smooth upgrades.
> So, if I read your request correctly, moving avahi-daemon from depends
> to recommends would be satisfactory?
You'd need to move all three of avahi-daemon, avahi-autoipd, and
libnss-mdns, because they work in concert. A convenient method may be
to create a recommends dependency on a separate "avahi-desktop"
package that depends on all three.
It's not an optimal solution, but it is a workable one. As I have
written at length on many occasions, avahi is insecure and unreliable
for users, imposes an unnecessary burden on the Internet at large,
and should be deprecated (certainly not installed by default). A
"suggests" dependency would require a conscious decision to activate
and is much preferred. However, moving "los tres diablos" to
recommends would at least allow a user to purge them and still
preserve smooth upgrades.