Gergely Gábor <elentirmo.gilgalad%gmail.com@localhost> writes: > i have noticed that cups has a dependency on mDNSresponder, if the > option dnssd is on. The same functionality is also provided by avahi, > that is gaining more and more support, and i wonder if the package > could be modified, to also support avahi, possibly on an OR-OR basis > with mDNSresponder. > > I don't know if there is a policy on globally seleceting a multicast > dns stack, but avahi does have a compatibility layer for > mDNSresponder. I don't think we have any policy. If cups can build against avahi, then one option is to add an avahi option to cups and let people use that if they want. Another option is to build avahi with the mDNSresponder compat layer (if not already), and add a /usr/pkgsrc/mk/mdns.mk and have that select a provider. If avahi has all the mindshare, and mDNSresponder is going away, then maybe having an mk file is not worth the effort.
Attachment:
pgpvtltjB3zI6.pgp
Description: PGP signature