Ben Gamari wrote: > Furthermore, I just attempted to remove the dependency on avahi > altogether by adding the following to task-base.bb, > > BAD_RECOMMENDATIONS = "avahi-daemon avahi-autoipd" > > Despite this, it pulled in both packages. This I am truly baffled by. Ideas?
I am not sure whether it will not break Zeroconf support in full builds of the same distro. Another possible solutions: - Branch a new minimal avahi-less distribution. - Split avahi to more parts (or even better, to more stages to allow complete build and prevent build loops), just to avoid unwanted build loops and dependencies. (core, stuff that require glib>k, mono stuff, qt3 stuff, qt4 stuff) and then include only low level avahi parts. The trick: http://avahi.org/ticket/222#comment:2 Avahi contains both low level and high level utilities. Library is required by many low level libraries. Low level daemons require only dbus. Python is required for avahi-bookmarks and other python utilities. GTK is required for avahi GUI. glib is required for avahi glib bindings. mono is required for avahi C# bindings. qt* is required for avahi qt* bindings. -- Stanislav Brabec http://www.penguin.cz/~utx/zaurus _______________________________________________ Angstrom-distro-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
