Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using libavahi-compat-libdnssd-dev package instead of current mDNSResponder installation #2376

Open
db00lean opened this issue Jul 12, 2024 · 1 comment

Comments

@db00lean
Copy link

As it stands the process of installing mDNS required headers and shared objects is quite cumbersome. Unpacking a tarball and applying 10 patches appears very roundabout and is one of the few unclean portions of ./script/bootstrap (seen here).

I'm not sure if it has already been considered, but it appears there is a package available on most distributions that contains the files required. libavahi-compat-libdnssd-dev is supported by the Avahi team, and is available on Ubuntu and OpenWRT. A simple apt-get install would remove the patch files from the repo, as well as some dependencies and extra steps that the current process requires.

The feature would be to validate that this package works the same as the current version of mDNS installed, and to update ./script/bootstrap with the new installation process.

@superwhd
Copy link
Contributor

If I understand correctly, this library libavahi-compat-libdnssd-dev provides mDNSResponder API while using Avahi as the backend?

I think the problem here is, there are different behaviors between Avahi and mDnsResponder so users may have different preferences of them, not just because of their APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants