Date: Thu, 16 Feb 2012 17:13:24 GMT From: Matthieu Volat <mazhe@alkumuna.eu> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/165206: wish: print/cups-base dnssd support with net/mDNSResponder Message-ID: <201202161713.q1GHDOUT042024@red.freebsd.org> Resent-Message-ID: <201202161720.q1GHK9nW075409@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 165206
>Category: ports
>Synopsis: wish: print/cups-base dnssd support with net/mDNSResponder
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 16 17:20:09 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Matthieu Volat
>Release: 9.0-RELEASE
>Organization:
--
>Environment:
FreeBSD freedom 9.0-RELEASE FreeBSD 9.0-RELEASE #3: Sat Jan 21 21:53:36 CET 2012 root@usbsd:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
Right now, the print/cups-base allows to have printer discovery only through the net/avahi-libdns compat port.
As the discovery seems to be developed around the net/mDNSResponder API, it should be safe to allow dnssd support through this port in addition of net/avahi-libdns version.
Since both ports are conflicting, there is no fear of mixing up the library used.
More : using net/mDNSResponder actually works (instead of hitting avahi bugs)
>How-To-Repeat:
make config in print/cups-base
>Fix:
Create a build option using avahi-libdns and another using mDNSResponder, specifying that both are mutually exclusives.
They uses almost the same configure options, the only difference being --with-dnssd-includes=${LOCALBASE}/include/ instead of --with-dnssd-includes=${LOCALBASE}/include/avahi-compat-libdns_sd/
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202161713.q1GHDOUT042024>