Reintroduce a bluetooth init.d script to trigger bluetooth devices after dbus is...
authorPacho Ramos <pacho@gentoo.org>
Mon, 9 Jan 2012 23:01:55 +0000 (23:01 +0000)
committerPacho Ramos <pacho@gentoo.org>
Mon, 9 Jan 2012 23:01:55 +0000 (23:01 +0000)
commita53dd584a9ab3e8be8c8cec0fa382507ab738df0
tree697e8ec889baae92a2574e0ddca103aaaf091185
parent6b167a651c87526d442cfcfea2085e28d0d1694a
Reintroduce a bluetooth init.d script to trigger bluetooth devices after dbus is started because, as talked with WilliamH, udev-postmount will be removed in the near future due upstream no longer detecting failed triggers at early boot. This should also solve bug 397673 by a.m. Drop old.

Package-Manager: portage-2.1.10.44/cvs/Linux x86_64
net-wireless/bluez/ChangeLog
net-wireless/bluez/Manifest
net-wireless/bluez/bluez-4.97-r2.ebuild [moved from net-wireless/bluez/bluez-4.97.ebuild with 90% similarity]
net-wireless/bluez/bluez-4.97-r3.ebuild [moved from net-wireless/bluez/bluez-4.97-r1.ebuild with 91% similarity]
net-wireless/bluez/files/bluetooth-init.d-r1 [new file with mode: 0644]