It is unclear what exactly USE=alsa does for bluez. The description states it adds "support" for alsa, while the ebuilds suggest MIDI support is enabled. To my knowledge, bluez 5 has removed the former "built-in" alsa support in favour of a pluggable architekture, where bluez-alsa is an implementation of an according plugin for alsa support. So alsa support probably requires media-sound/bluez-alsa. I don't know what is going on with the MIDI support, but I'd speculate that that is still a built-in part of bluez (although it is strictly coupled to alsa?) and that is also what the USE flag concerns. Based upon that speculation, I think the current USE=alsa should be renamed USE=midi and an actual USE=alsa should be added which pulls in media-sound/bluez-alsa (not sure whether in addition, bluez has to get a configure switch for support it).
It adds midi support via alsa-lib usage
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d0fe48785cce688dd6838794c810a3786c1bc1ef commit d0fe48785cce688dd6838794c810a3786c1bc1ef Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2019-06-10 11:22:54 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2019-06-10 11:22:54 +0000 net-wireless/bluez: Backport lots of fixes (from Fedora)... - Include multiple fixes backported by Fedora people - Stop relying on plugdev group and follow upstream policy (#679034) - Update udevadm PATH for current systemd (#539844) - Rename USE alsa to midi (#658862) Closes: https://bugs.gentoo.org/679034 Closes: https://bugs.gentoo.org/658862 Bug: https://bugs.gentoo.org/539844 Package-Manager: Portage-2.3.67, Repoman-2.3.13 Signed-off-by: Pacho Ramos <pacho@gentoo.org> net-wireless/bluez/Manifest | 1 + net-wireless/bluez/bluez-5.50-r3.ebuild | 267 +++++++++++++++++++++ .../bluez/files/bluez-5.50-sink-connect.patch | 72 ++++++ .../bluez/files/bluez-udevadm-path-r1.patch | 10 + net-wireless/bluez/metadata.xml | 9 +- 5 files changed, 354 insertions(+), 5 deletions(-)
