History

Breadway 99cc0a4717 All checks were successful Mirror to GitHub / mirror (push) Successful in 3s Details Extract breadhelp to its own repo (git.breadway.dev/Breadway/breadhelp) Mirrors the bos-settings extraction (`664298b`): a breadhelp release no longer requires a v* tag on the whole bos monorepo, which was indistinguishable from an actual BOS-version release tag. Source lives at ~/Projects/breadhelp now, full history preserved via git-filter-repo. Root Cargo.toml/Cargo.lock and .forgejo/workflows/package.yml removed too — breadhelp was the sole workspace member and the sole thing that workflow built.	2026-07-15 19:20:23 +08:00
..
README.md	Extract bos-settings to its own repo; add breadhelp; JSON-driven Hyprland config	2026-07-05 09:16:14 +08:00

Mirror to GitHub / mirror (push) Successful in 3s

Details

Extract breadhelp to its own repo (git.breadway.dev/Breadway/breadhelp)

Mirrors the bos-settings extraction (664298b): a breadhelp release no
longer requires a v* tag on the whole bos monorepo, which was
indistinguishable from an actual BOS-version release tag. Source lives
at ~/Projects/breadhelp now, full history preserved via git-filter-repo.

Root Cargo.toml/Cargo.lock and .forgejo/workflows/package.yml removed
too — breadhelp was the sole workspace member and the sole thing that
workflow built.

2026-07-15 19:20:23 +08:00

README.md Extract bos-settings to its own repo; add breadhelp; JSON-driven Hyprland config 2026-07-05 09:16:14 +08:00

README.md

Arch packaging

breadhelp/PKGBUILD builds and installs breadhelp from source — BOS's onboarding + help center, and the only first-party pacman package still built from this repo.

bos-settings is also pacman-packaged and served from the same [breadway] repo, but its source lives in its own repo now (~/Projects/bos-settings, github.com/Breadway/bos-settings) so a bos-settings release doesn't require a BOS ISO release.

Everything else the bread ecosystem ships (breadbar, breadbox, breadpad, ...) is bakery-managed, not pacman-packaged — see build-local.sh.

Local build

cd breadhelp && makepkg -si

Before publishing to [breadway] repo

CI (.forgejo/workflows/package.yml) handles this on tag push (vX.Y.Z): it bumps pkgver, archives the repo into the expected tarball name, and runs makepkg. To do it by hand instead:

Tag a release on GitHub (vX.Y.Z).
Update pkgver in breadhelp/PKGBUILD to match the tag.
Update source to the release tarball URL.
Run updpkgsums (or manually set sha256sums).

Runtime dependencies

Package	Required	Notes
`gtk4`	yes	UI toolkit
`glib2`	yes	always
`snapper`	optional	create-backup one-click fix