Should raise an error when adding a INET6 service while IPv6 is not enabled.

[cassidy]

To reproduce: - be sure that ipv6 is disabled in avahi-daemon.conf - create a new entry group - call AddService? with PROTO_INET6 as protocol on this entry and then Commit - the service is not announced on the network and AddService? doesn't raise an error.

Avahi should raise an error when trying to announce an INET6 service while IPv6 is not activated.

Tested with Avahi 0.6.23

[lennart]

Hmm, I am not convinced a check like this is really something we want. I mean, we don't check for valid interfaces either, and that is good that way, since interfaces come and go. And that's the same with IPv6 too: based on runtime reconfiguration IPv6 and IPv4 might come and go too.

I don't thin AddService? should be misunderstood as a function to check whether a certain protocol is activated in Avahi or not, or a specific interface is available or not. Because if we would implement this checking we'd also have to add a notification framework for letting clients know when this changes.

So, I think adding a check like this is not a good idea. Clients should register everything they want, and consider Avahi a black box that then makes the best of it.