server has zeroconf? ( !avahi? (|| (...) ) ) dep and use zeroconf && ! use avahi && dnssd="--enable-dnssd" client has zeroconf? ( || (...) ) dep and $(use minimal && echo "--disable-dnssd" || echo "$(use_enable avahi dnssd)") --disable-avahi server is probably correct, as avahi is upstream default in this version.
Seeing as samba 3.4.2 was added to the tree, still having this problem, I'm pinging you, samba people, for some input and elaborating a bit. I don't really use samba (though, probably a few packages on my system link with samba libs). This bug was created as an effect of a forum thread, where a user IIRC had avahi useflag set, but not zeroconf (or the other way around). The effect was a build failure. For me, it looks like server ebuild was correctly updated, when upstream started using (and preferring) avahi, but client ebuild missed that update.
OK, this is the thread I was referring to. But, as I already mentioned, the correct fix is probably making the same changes in client, as they were made in server.
Created attachment 209594 [details, diff] patch for the client Following IRC discussion: - disabling dnssd support (as per upstream default) - avahi support controlled by zeroconf useflag
Created attachment 209595 [details, diff] patch for the server
Any reason you're using the zeroconf USE-flag and not avahi? From /usr/portage/use.desc: avahi - Add avahi/Zeroconf support zeroconf - Support for DNS Service Discovery (DNS-SD)
It's back to one ebuild now :)
