I prefer (so far) to use avahi - it has more features. Eventually I think slimserver must be configurable somehow, to use either one. Reproducible: Always Steps to Reproduce: emerge slimserver Actual Results: installs mDNSResponder after I have unblocked it... Expected Results: USE flags, or some kind of conf file, should control whether to use avahi or mDNSResponder (or possibly other choices) as the service-announcement daemon
Created attachment 120750 [details, diff] slimserver-6.5.1.ebuild.diff So, does it work for you with the following ebuild patch and avahi compiled w/ USE=mdnsresponder-compat? If not, sorry but you'll need to take this upstream.
This will require an upstream change since, IIRC, slimserver invokes mdnsresponder command line programs.
Comment on attachment 120750 [details, diff] slimserver-6.5.1.ebuild.diff Closing then.