Tests that read ../../../mesh-catalog or ../../../mesh-host gave a verdict that depended on what sat beside the checkout: a stale or dirty sibling failed them on a desktop, and a missing one skipped them unseen. They now read the clone the build seat puts in MESH_CHECK_BESIDE, failing when it is absent there, and elsewhere a copy captured at a named commit. The skip had hidden that the builder test read a module retired by ADR 0190. The systemd reading test no longer counts the machine's own environment.d.
54 lines
992 B
Plaintext
54 lines
992 B
Plaintext
{
|
|
"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"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
}
|