You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 simpleapt-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.
The text was updated successfully, but these errors were encountered: