GTK4 control panel for BOS (Bread Operating System)
9c85a89297
Adapter power switch, paired devices (connect/disconnect/forget), and scan-for-new-devices with pairing -- BOS had bluez/bluez-utils packaged and bread's own daemon already monitors Bluetooth events, but there was no GUI to actually manage devices anywhere in the settings app. Shells out to bluetoothctl's non-interactive mode, same "standard CLI, no new dependency" choice as Network (nmcli) and Snapshots (snapper). Pairing only covers "just works" SSP (most audio/HID devices) -- a device requiring a PIN would need this app to register its own bluetoothd agent, out of scope for now; it just fails with the reason shown, same honest-failure pattern the Firewall fix added. |
||
|---|---|---|
| .forgejo/workflows | ||
| packaging | ||
| src | ||
| .gitignore | ||
| bakery.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
bos-settings
System settings app for BOS (Bread Operating System) — GTK4, configures every bread* app's config plus core system settings (network, sound, power, users, firewall, snapshots, packages, AUR, firmware, Hyprland display/appearance/autostart) non-destructively.
Split out of the bos repo into its own repo so a bos-settings release doesn't require a BOS ISO release, and vice versa. Still the only pacman-packaged (not bakery-managed) bread app — see packaging/README.md.
Building
cargo build --release
Packaging / releasing
See packaging/README.md. In short: bump Cargo.toml's version, tag vX.Y.Z, push the tag to both remotes — .forgejo/workflows/package.yml builds and publishes to the [breadway] pacman repo automatically.