Files
bearhub/packaging/aur
Sebastian Palencsar e95a23bc20 M3 namespace migration: complete Phase B, partial Phase D, docs and tests
- Native runtime under bearhub/ (api, commons, gems, view/util, view/core, view/qt)
- bauh/ compatibility re-export shims for legacy imports
- Phase D: canonical __version__/__app_name__ in bearhub/__init__.py; pyproject.toml
  and setup.py point at bearhub package
- Native gem loader at bearhub/view/core/gems.py
- Namespace compatibility tests (159 tests passing)
- Documentation: CHANGELOG [Unreleased], NAMESPACE_MIGRATION, ROADMAP, README,
  CONTRIBUTING, docs/qt6-migration.md, packaging/aur/README.md
2026-06-27 10:26:41 +02:00
..

AUR Packaging

This directory contains starter PKGBUILD files for publishing Bearhub on the AUR:

  • bearhub/PKGBUILD: stable package from tagged releases
  • bearhub-git/PKGBUILD: rolling package from main

Before publishing:

  1. Generate .SRCINFO with makepkg --printsrcinfo > .SRCINFO inside each package directory.
  2. Build-test locally with makepkg -si.
  3. Push each package to its own AUR Git repository (aur@aur.archlinux.org:bearhub.git and aur@aur.archlinux.org:bearhub-git.git).

Stable release checklist (bearhub)

  1. Move CHANGELOG.md [Unreleased] entries under the new tag (e.g. 0.10.7-bearhub.7 or 0.10.8).
  2. Commit all release changes on main.
  3. Create and push the git tag:
    git tag -a 0.10.7-bearhub.7 -m "Release 0.10.7-bearhub.7"
    git push origin main
    git push origin 0.10.7-bearhub.7
    
  4. Refresh tarball checksum in bearhub/PKGBUILD:
    cd packaging/aur/bearhub
    makepkg -g >> PKGBUILD  # or updpkgsums after source URL is reachable
    makepkg --printsrcinfo > .SRCINFO
    
  5. Sync to local AUR clones:
    scripts/sync-aur-packaging.sh
    
  6. Build-test both AUR packages, then publish AUR commits.
  7. Optional: create GitHub release from the new tag.