Remove orphaned bakery.toml; correct README's stale claim

breadlock isn't in bread-ecosystem/registry/bread-ecosystem.toml and
package.yml (the only release workflow this repo has) never reads
bakery.toml — it only touches packaging/arch/PKGBUILD. So the file was
dead metadata, and the README's claim that "bakery.toml is the
bread-ecosystem package index entry" was stale/incorrect: it never
actually was one. breadlock ships pacman-only, which makes sense for a
PAM/greeter component — README now says so explicitly.
This commit is contained in:
Breadway 2026-07-17 14:03:18 +08:00
parent 38aede9126
commit 9df32b1917
2 changed files with 1 additions and 16 deletions

View file

@ -54,7 +54,7 @@ sudo pacman -S gtk4 wayland libxkbcommon pam rust cargo
## Packaging
`packaging/arch/PKGBUILD` builds and installs both binaries plus `/etc/pam.d/breadlock`. `bakery.toml` is the bread-ecosystem package index entry.
`packaging/arch/PKGBUILD` builds and installs both binaries plus `/etc/pam.d/breadlock`, published to the `[breadway]` pacman repo by `.forgejo/workflows/package.yml`. breadlock is pacman-only — it is not in bread-ecosystem's registry and has no `bakery.toml`; a PAM/greeter component gets installed through the package manager, not the bakery curl-script channel.
**Not included, by design**: this repo does not touch `/etc/greetd/config.toml`, install a lock keybind, or wire up `hypridle`. Once packaged, wiring BOS to actually use these binaries means:

View file

@ -1,15 +0,0 @@
name = "breadlock"
description = "Session locker and greetd greeter for Hyprland / Wayland"
binaries = ["breadlock", "breadgreet"]
system_deps = ["pam", "wayland", "libxkbcommon", "gtk4"]
optional_system_deps = ["cage", "hyprland"]
bread_deps = []
[config]
dir = "~/.config/breadlock"
example = "breadlock.example.toml"
[install]
post_install = [
"echo 'breadlock installed. /etc/pam.d/breadlock is installed by the package; wiring greetd (cage -s -- breadgreet) and a lock keybind/hypridle is a separate manual step.'",
]