On Tue, 2013-08-06 at 14:39 -0300, Jo?o Paulo Rechi Vita wrote: > On Mon, Jul 29, 2013 at 8:49 AM, Tanu Kaskinen > <tanu.kaskinen at linux.intel.com> wrote: > > No, I don't think there's any way to forbid users from loading specific > > modules. If you don't want to drop module-bluez5-device altogether (and > > instead implement it as a part of the bluez5-util library), there could > > be a "loaded_by_discovery" module argument which would have to be passed > > to module-bluez5-device, otherwise the module would fail to load (with > > an informative error message). > > > > When I was going to implement this approach I had a different idea: we > can simply rely on the presence of bluez5-discovery in the shared > hashmap of pulseaudio's core to tell if module-bluez5-discovery has > been loaded or not. In other words, we fail loading > module-bluez5-device if bluez5-discovery is not found. Good idea! -- Tanu
