Bug 211571 - net/netatalk3: zeroconf selection does not work
Summary: net/netatalk3: zeroconf selection does not work
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Joe Marcus Clarke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-04 07:10 UTC by Daniel Becker
Modified: 2016-08-05 20:33 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (marcus)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Becker 2016-08-04 07:10:36 UTC 
The netatalk3 port has a config switch to select either Avahi or mDNSResponder as the zeroconf implementation. However, the port's configure script automatically selects an implementation based on installed headers and libraries, and it prioritizes Avahi over mDNSResponder if both are installed.
Comment 1 Daniel Becker 2016-08-04 07:15:12 UTC 
In fact, it will pick Avahi even if only net/avahi-app, but not the actual avahi daemon from net/avahi is installed (which was the case on my machine) -- and in this case, the result is that registration with avahi fails and netatalk cannot advertise its services.
Comment 2 commit-hook freebsd_committer freebsd_triage 2016-08-05 20:33:12 UTC 
A commit references this bug:

Author: marcus
Date: Fri Aug  5 20:32:11 UTC 2016
New revision: 419708
URL: https://svnweb.freebsd.org/changeset/ports/419708

Log:
  Ensure that Avahi supprt is disabled if mDNSResponder is
  chosen for Zeroconf.

  PR:		211571

Changes:
  head/net/netatalk3/Makefile
Comment 3 Joe Marcus Clarke freebsd_committer freebsd_triage 2016-08-05 20:33:59 UTC 
The problem with mDNSResponder not being used should now be fixed.  However, avahi-app does include avahi-daemon.  So I don't think we need to switch the dependencies.