diet-guard/packaging
Krzysztof kuhy Rudnicki 4cd8e368b8
Some checks are pending
pre-commit / pre-commit (push) Waiting to run
Tests / test (3.10) (push) Waiting to run
Tests / test (3.11) (push) Waiting to run
Tests / test (3.12) (push) Waiting to run
release-apk / release (APK) (push) Waiting to run
packaging/aur: sharpen metadata against the AUR submission rules
The AUR does not review uploads, but packages that violate the rules "may be
deleted without warning", so these were audited against the submission
guidelines rather than assumed compliant.

- pkgdesc now says what the app actually does, in terms a stranger can judge.
  "Usefulness" is the one rule these packages are genuinely exposed to, and
  the old wording led with the implementation detail.
- optdepends lists every browser the wrapper actually probes for. It searched
  Thorium and Brave but only advertised Chrome and Chromium; all four names
  were checked to resolve in the official repos or the AUR.

Verified compliant on the rules that can be checked mechanically: not in an
official repo, name free in the AUR, x86_64 declared, no replaces= (the AUR
reserves it for renames), Maintainer line present, license installed. The
conflicts=('todo') on todo-flutter is justified, not defensive: AUR 'todo'
2.4-1 installs its own /usr/bin/todo, confirmed by reading its PKGBUILD.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Aoa1nKWRrAbowz7Hfd3tgL
2026-08-09 23:51:18 +02:00
..
aur packaging/aur: sharpen metadata against the AUR submission rules 2026-08-09 23:51:18 +02:00