I've fixed the dbus ticket and committed all the bluez updates in my local 
repo, but I'm reluctant to commit the entire set of changes to the OpenWrt svn 
as the size of the bluez-utils package is jumping from ~140k to ~250k.  I've 
been playing with the configure opts and can drop the size down to ~110k by 
passing --disable-all, but haven't figured out exactly which "extra" options 
are causing the massive size increase.

If there are major improvements between 2.24 and 3.24 -- or the modified 
configure args -- that warrant the extra size increase I'll commit the 
changesets, otherwise I wonder if staying up to date is worth the potential 
bloat.

-Andy

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to