-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27.05.2012 03:17, Jeroen van Bemmel wrote: > Yes, but we probably want to keep people from installing both at > the same time. Any idea how to handle that nicely?
I think thats easy possible like on PA/avahi (no)dbus ...; Works, I started splitting bluez(4.99) up into the daemons, lib and utils now (very granular as I hate bloated packages myself..) The main question is still: how to name it? What to consider (never used pand or dund myself..) Calling it bluez* is confusing, rename the bluez*3.36 to bluez3 and new to bluez4-* ? or? I'm happy to provide patches for, but need some thoughts and a direction.. Michael P.S.: As it's on topic, did anyone play with BT4.0 LE yet ? (Intro: http://www.rtcwirelessmag.com/?p=150) It sounds very interesting for OpenWRT-Boxes I think ;) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/Cl+MACgkQaWRHV2kMuAIBMgCg/HLAAHeZo4BGCiz1KXCioqpU j5cAoOSSrl6IQgrk6cNoXKE0JdGk6+Mn =ZlJO -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
