Breadway d3517d1433 Allow well-formed bread.command events on the emit bus

Docs already said any module or app could publish bread.command.<app>.<verb>,
but command is reserved so both unsourced bread-emit and sourced App emit
rejected the whole namespace. Keep command unclaimable as an app id; accept
bread.command.<known-app>.<verb> (and let an app command another known app).
Also ship bread-emit and bread-module-host, and give udev enumerate the same
classification fields as a live add so boot-time devices are not all unknown.

2026-08-15 21:41:40 +08:00

1 KiB

Raw Blame History

Packaging

This directory contains distribution packaging for Bread.

packaging/
└── systemd/
    └── breadd.service    ← systemd user service unit

Prebuilt binaries are distributed exclusively via bakery (see the main README) — there is no Arch/pacman package for bread anymore. bakery installs the systemd user service unit itself, matching the packaging/systemd/breadd.service file here.

systemd user service

The service unit starts breadd as a user service after the graphical session is available.

# Install and enable manually (if not using bakery)
mkdir -p ~/.config/systemd/user
cp systemd/breadd.service ~/.config/systemd/user/
systemctl --user daemon-reload
systemctl --user enable --now breadd

# Check status
systemctl --user status breadd
journalctl --user -u breadd -f

The service sets RUST_LOG=info by default. To increase verbosity, override it in a drop-in:

# ~/.config/systemd/user/breadd.service.d/debug.conf
[Service]
Environment=RUST_LOG=debug

1 KiB Raw Blame History

Packaging

systemd user service

1 KiB

Raw Blame History