Hi there. I'm looking for a bit of advice on two issues concerning the Avahi package.
Avahi provides zero-configuration services, similar to Apple's Bonjour, see http://www.avahi.org Avahi can be compiled with or without D-BUS support (see http://www.freedesktop.org/wiki/Software/dbus), and the current OpenWRT package compiles it without D-BUS support. The advantage, of course, is that D-BUS need not be included in the system to get the basic Avahi services: a device name and a self-assigned IP number. The disadvantage is that the more advanced facilities that require the D-BUS interface of Avahi are not available; so the functionality of avahi-publish (dynamically publish and alter services) and avahi-browse (monitor published services on the network) are not available, nor (AFAIK) are the so-called avahi-client APIs. So here are the two issues I'm wondering about: Issue 1: It would be nice to have the choice of either the 'simple' current version of avahi without D-BUS or the 'full' version of avahi with D-BUS. Question: How should I do that? Should I create a new set of packages, called, say, avahi-with-dbus...? Or should I just put some kind of a flag in the Makefile of the existing avahi package? Issue 2: avahi-daemon is configured to be loaded (START=50) by the init.d mechanism _before_ D-BUS (START=60), so, as things stand, a D-BUS-enabled avahi-daemon won't start up properly because D-BUS won't be running when it attempts to load. Question: Is it best just to leave D-BUS alone completely and change the START number for avahi, say to 70, so that it loads after D_BUS? Any advice or pointers gratefully received! Mike Brady _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
