Bug 285822 – net-fs/samba-server-3.3.7 and net-fs/samba-client-3.3.7 handle avahi useflag inconsistently

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Rafał Mużyło 2009-09-21 11:24:01 UTC]

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.

[Comment 1 Rafał Mużyło 2009-10-09 18:37:45 UTC]

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.

[Comment 2 Rafał Mużyło 2009-10-15 16:54:51 UTC]

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.

[Comment 3 Rafał Mużyło 2009-11-08 00:49:55 UTC]

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

[Comment 4 Rafał Mużyło 2009-11-08 00:50:28 UTC]

Created attachment 209595 [details, diff]
patch for the server

[Comment 5 Ewoud Kohl van Wijngaarden 2010-02-18 17:13:23 UTC]

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)

[Comment 6 Patrick Lauer 2010-10-17 08:10:09 UTC]

It's back to one ebuild now :)