From 2e32488b26a77d2373c933c9b32e796d089014aa Mon Sep 17 00:00:00 2001 From: Breadway Date: Fri, 17 Jul 2026 14:02:59 +0800 Subject: [PATCH] =?UTF-8?q?Remove=20orphaned=20bakery.toml=20=E2=80=94=20n?= =?UTF-8?q?othing=20serves=20it?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit breadarr has no .forgejo/workflows at all (no mirror, release, or package workflow) and no PKGBUILD, and it isn't listed in bread-ecosystem's registry/bread-ecosystem.toml, so gen-index.sh would never pick it up even if a release workflow existed. The bakery.toml here was pure dead metadata. Not wiring up a release workflow instead: breadarr isn't in the registry and its distribution channel (bakery, pacman, both, neither) hasn't actually been decided, so adding one here would be inventing a channel commitment I have no signal for. If/when breadarr is ready to ship, follow docs/release-channels.md in bread-ecosystem to add it properly (bakery.toml + registry entry + release.yml, or a PKGBUILD + package.yml, or both). --- bakery.toml | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 bakery.toml diff --git a/bakery.toml b/bakery.toml deleted file mode 100644 index cad7a26..0000000 --- a/bakery.toml +++ /dev/null @@ -1,21 +0,0 @@ -name = "breadarr" -description = "Lightweight Sonarr/Radarr/Prowlarr replacement" -binaries = ["breadarrd", "breadarr-tui"] -# breadarr runs natively (not in Docker), so unlike the old Sonarr/Radarr/ -# Prowlarr containers it needs these on the host PATH directly. -system_deps = ["mkvtoolnix-cli", "ffmpeg"] -optional_system_deps = [] -bread_deps = [] - -[[service]] -unit = "breadarrd.service" -enable = true - -[config] -dir = "~/.config/breadarr" -example = "config.example.toml" - -[install] -post_install = [ - "systemctl --user is-active --quiet breadarrd || systemctl --user start breadarrd", -]