On Tue, 2018-03-20 at 11:24 +0200, Luiz Augusto von Dentz wrote: > Hi, > > On Mon, Mar 19, 2018 at 11:35 PM, Felipe Sateler <fsateler at debian.org> wrote: > > > > > > On Mon, Mar 19, 2018 at 5:39 AM, Luiz Augusto von Dentz > > <luiz.dentz at gmail.com> wrote: > > > > > > From: Luiz Augusto von Dentz <luiz.von.dentz at intel.com> > > > > > > Since there is no longer support for BlueZ 4 it makes no sense to keep > > > BlueZ 5 modules separated. > > > > > > > AFAICT, this would render invalid many configuration files as they would > > refer to module-bluez5-*. Is this desirable? > > You mean there are some configuration that still needs changing or you > are referring to the fact that default.pa should be updated? I suppose > the latter happens all the time when there is a new module, but > perhaps we want some alias so distros don't have the trouble of > changing bluez to bluetooth. Yes, module-bluez5-discover should be an alias for module-bluetooth- discover. There are examples of similar cases: module-combine just loads module-combine-sink and warns about the deprecated module name. module-bluez5-device probably doesn't need to be kept, because the discover module is responsible for loading the device modules, and AFAIK trying to load the device module manually without the discover module doesn't work. Having a separate device module doesn't really serve any purpose, it would be nice to get rid of it altogether. -- Tanu https://liberapay.com/tanuk https://www.patreon.com/tanuk
