-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 21.11.2011 14:48, schrieb Mike Brady: > ... > > Packages that don't require D-BUS support are compiled with D-BUS > support disabled by default, keeping the build as small as > possible. Support for D-BUS can be selected if desired. > > Selecting packages that require D-BUS support -- avahi-utils or > libavahi-client -- will automatically cause all packages to be > built with D-BUS support and will add the D-BUS package to the > build.
Good so far, I'm using avahi heavily but back in Nov this sounded well to me, no reason to complain so nothing to say ;) Now having update to latest trunk I ran into one thing: When putting avahi-daemon (no dbus needed there at first) into the base image and building the remainder (libavahi-client etc.) as addon-packages to get post-installed as needed, the image-included avahi-daemon won't run. Clear so far, it was build with dbus but there is no lib/dbus. Wouldn't it be neater to have two packages there ? Something like avahi-daemon (no dbus compiled in) avahi-daemon-dbus So one can choose to include avahi but without all the overhead and still install the dbus-support later on as required. i.e. like it's done with the pulseaudio-daemon/pulseausio-daemon-avahi packages best regards Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8jSS0ACgkQaWRHV2kMuAJ7BACgu60huijHZtuOx5buFkJpbu1R 5YMAoJvOqfZ2l8773uO/w15fyLmKnr7h =jnGD -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
