Currently this ebuild only has "zeroconf" USE flag for handling avahi vs mDNSResponder deps. I would prefer take cups-1.3.7-r1.ebuild as example and create a flag called "avahi" for adding avahi support, as all other implementations are being deprecated and most avahi users will only have "avahi" USE flag in make.conf. Cups has the following in DEP: avahi? ( net-dns/avahi ) zeroconf? ( !avahi? ( net-misc/mDNSResponder ) ) and also tests: if use avahi && ! built_with_use net-dns/avahi mdnsresponder-compat ; then echo eerror "In order to have cups working with avahi zeroconf support, you need" eerror "to have net-dns/avahi emerged with \"mdnsresponder-compat\" in your USE" eerror "flag. Please add that flag, re-emerge avahi, and then emerge cups again." die "net-dns/avahi is missing the mdnsresponder-compat feature." fi Thanks Reproducible: Always
agree, in fact i'm stuck by this behavior :( [blocks B ] net-dns/avahi ("net-dns/avahi" is blocking net-misc/mDNSResponder-107.6-r5) [blocks B ] net-misc/mDNSResponder ("net-misc/mDNSResponder" is blocking net-dns/avahi-0.6.23) equery d mDNSResponder [ Searching for packages depending on mDNSResponder... ] kde-base/kdelibs-3.5.10 (!avahi & !bindist? net-misc/mDNSResponder) net-misc/ntp-4.2.4_p5 (zeroconf? net-misc/mDNSResponder) net-print/cups-1.3.9 (zeroconf & !avahi? net-misc/mDNSResponder)
said USE flags were added by other people. you'll have to either provide a fix or wait for someone who actually knows/cares about these to provide a patch.
I close this as this would go against zeroconf USEs "unification" suggested in: http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg31489.html