Any opinions/objections to adding Requires: nss-mdns to kdelibs? I've been asked by kde upstream to consider adding it, else zeroconf (ie, interfaces provided by libkdnssd) is non-functional.
Now, It's not strictly a *hard* dep per se, and I'd be happy either adding it only to kde-spin and/or comps too (or doing nothing). what say you?
There's a wee bit of history here to consider too... it's not been added to comps default yet, due to some (?) unresolved objections from the glibc maintainer. But... it *is* installed by default on the (gnome) desktop spin.
-- Rex
On Mon, 26 Jan 2009, Rex Dieter sent out 0.7K bytes to say:
Any opinions/objections to adding Requires: nss-mdns to kdelibs? I've been asked by kde upstream to consider adding it, else zeroconf (ie, interfaces provided by libkdnssd) is non-functional.
Now, It's not strictly a *hard* dep per se, and I'd be happy either adding it only to kde-spin and/or comps too (or doing nothing). what say you?
There's a wee bit of history here to consider too... it's not been added to comps default yet, due to some (?) unresolved objections from the glibc maintainer. But... it *is* installed by default on the (gnome) desktop spin.
Well, one one hand, it isn't encouraged to use the nss_mdns plugin (somewhere on avahi site) but it does provide one easy way for apps to resolve a .local host.
I think; however, that the principle of minimal surprise would encourage us to ensure it is installed, regardless of the harazds (a core function like resolving being dependant on a user-level app, especially in Fedora where avahi's ports are often blocked by the default firewall)