Hi Jiri, I'm writing the below hints mostly from reading the tool's manpages, because I have not used them ever (and I have done some debugging on bluetooth issues during the last 15 years... ;-) Am 17.12.19 um 14:36 schrieb Jiri Slaby:
On 16. 12. 19, 15:39, Stefan Seyfried wrote:
The first step will be to split them off into a "bluez-deprecated" package, which contains the following binaries:
/usr/bin/ciptool
This is a tool for managing the "Bluetooth Common ISDN Access Profile (CIP)", I'd guess that boxes like the old BlueFritz! bluetooth isdn adapter probably might need this. I doubt this is still in use by anyone.
/usr/bin/gatttool
This is something about Bluetooth Low Energy (BLE) IIUC, I'd guess its functionality will be available via bluetoothctl nowadays.
/usr/bin/hciattach
A tool to connect serial UART Bluetooth devices. Newer tool is btattach.
/usr/bin/hciconfig /usr/bin/hcitool /usr/bin/sdptool
bluetoothd together with bluetoothctl
/usr/bin/hcidump
btmon (hcidump actually is the one that needs security patches that upstream no longer wants to include)
/usr/bin/rfcomm
bluetoothd together with bluetoothctl
In the not too far future, the bluez-deprecated package will be dropped and bluez will be built without "--enable-deprecated". If I had to guess now, I would say that "not too far future" means "end of 2020".
Perhaps you can also point us to some document defining in favor of what they are deprecated. I.e. what we are supposed to use instead of the above?
I have listed the replacements as far as I know them above below the tools, other tools (or snippets for writing your own) are in the bluez-test package, which consists mostly of small python demo applications. Basically the upstream reasoning for deprecating these tools is that bluetoothd as the central service is handling all this in a coordinated way and should be used (vie bluetoothctl or desktop applets) to perform the tasks that these tools did. As an example, a manual "hcitool scan" did interfere with things bluetoothd does and settings done with "hciconfig" were not persisted anywhere (and bluetoothd did not know about them and thus did not work correctly), so this is why these tools were deprecated. At least that's how I understood it :-) I have been using bluetoothctl for almost all my configuration and debugging tasks and could perform all tasks that I needed. It's even better than using a desktop applet, since I can copy and paste the bluetoothctl commands easily into a HOWTO or a bug report ;-) Have fun, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org