Bug 211345 - dns/nss_mdns: remove in favor of mDNSResponder_nss ?
Summary: dns/nss_mdns: remove in favor of mDNSResponder_nss ?
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Ashish SHUKLA
URL:
Keywords: needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2016-07-24 19:17 UTC by Adam Goode
Modified: 2019-01-31 01:32 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Goode 2016-07-24 19:17:18 UTC
I am looking at updating the upstream nss-mdns (though I am not the maintainer) and was wondering if the BSD portion of the code is still relevant. I noticed that the BSD support in the upstream code doesn't do anything without patches found in the ports tree.

Is there interest in upstreaming these ports packages? Or could I suggest removing the BSD code from upstream nss-mdns if mDNSResponder_nss is the new way for BSD?
Comment 1 Matthieu Volat 2016-07-25 06:18:19 UTC
Hello, just my 2c as the mDNSResponder_nss maintainer,

You can't really say that either is officially endorsed: despite its generic name, dns/nss_mdns is the Avahi plugin whereas dns/mDNSResponder_nss is for Apple's (reference) mDNSResponder implementation.

As of now, both can be installed concurrently on FreeBSD, but the user/packagers must choose which NSS module to install since they register a library with the same name in the filesystem and nsswitch.conf.

Note that to use mDNSResponder, I had to write some wrapper code. It was not proposed to upstream because I'm not sure on how to contact them, and I thought their interest would be low. Since that code relies on quite stable APIs, I'm happy with the situation for now :)
Comment 2 Adam Goode 2016-07-25 12:10:45 UTC
Hi Matthieu,

Thanks for the comment. It helps clarify my understanding of the situation.

With this understanding, here is my plan:

- propose to the new Avahi upstream (https://github.com/lathiat/avahi) that they become the definitive upstream for nss-mdns
- if they agree, then I will merge the existing nss-mdns repository into Avahi's
- then, unifdef many of the compile options, specifically the non-Avahi support which has been long deprecated
- fix up and merge the outstanding FreeBSD ports patches
- then finally look into adding some new functionality to nss-mdns

(Note that this is a best effort project on my part. It's mostly a yak-shave based on interest in fixing crbug.com/626377.)

If there is nothing else to discuss here, please close this bug. Thanks!
Comment 3 Adam Goode 2016-07-25 22:41:00 UTC
Follow https://github.com/lathiat/avahi/issues/64 for updates on the new potential upstream location of nss-mdns.
Comment 4 Ashish SHUKLA freebsd_committer 2016-07-27 07:21:41 UTC
Hi Adam,

Thanks for opening this PR. I can help with testing FreeBSD stuff. ATM, I'm not using Avahi,  as IIRC my experience with nss_mdns was not very great/reliable in the last few months, which is why I stopped using Avahi altogether.

I can double check to see if anything has changed, by this weekend, and confirm how good are the patches.

Ashish
Comment 5 Tobias Kortkamp freebsd_committer 2019-01-27 07:42:39 UTC
(In reply to Ashish SHUKLA from comment #4)
Any news?
Comment 6 Ashish SHUKLA freebsd_committer 2019-01-31 01:32:17 UTC
(In reply to Tobias Kortkamp from comment #5)

Sorry, didn't get to try it, other things in life took priority, and it got lost. I will make time for it, and will review it by February 14, 2019 when I get back to my FreeBSD computer.

If you get to try it, or are interested in maintaining it, then please let me know, I'll pass it on.

Thanks!