jochen
3b43a1ef4d
bluez and bluez-utils, and bluetooth.service running and enabled. On both workstations bluez is installed only as a dependency; declaring it keeps a clean-up from taking it. Nine Go tools over bluetoothctl: controller, power, devices with battery where reported, a bounded scan, connect, disconnect, trust, pair (an agent that confirms nothing, for headphones) and remove. An act whose output says it failed is an error whatever the exit status, and one bluez refuses the account is repeated through sudo -n.
54 lines
992 B
JSON
54 lines
992 B
JSON
{
|
|
"module": "bluetooth",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"package-manager",
|
|
"service-manager"
|
|
],
|
|
"tools": [
|
|
"bluetooth_controller",
|
|
"bluetooth_power",
|
|
"bluetooth_devices",
|
|
"bluetooth_scan",
|
|
"bluetooth_connect",
|
|
"bluetooth_disconnect",
|
|
"bluetooth_trust",
|
|
"bluetooth_pair",
|
|
"bluetooth_remove"
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "stack",
|
|
"type": "package",
|
|
"package": "bluez"
|
|
},
|
|
{
|
|
"id": "utilities",
|
|
"type": "package",
|
|
"package": "bluez-utils"
|
|
},
|
|
{
|
|
"id": "daemon",
|
|
"type": "service",
|
|
"unit": "bluetooth.service",
|
|
"state": "running",
|
|
"boot": "enabled"
|
|
}
|
|
],
|
|
"build": {
|
|
"artifacts": [
|
|
{
|
|
"name": "tools",
|
|
"kind": "bundle",
|
|
"language": "go",
|
|
"system": "arch",
|
|
"from": "cmd/bluetooth-tools",
|
|
"binary": "bluetooth-tools",
|
|
"loads": [
|
|
"bluetooth-tools"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
}
|