Warning: This is an extremely early version. We're just testing ideas. Implementation might change completely.
PacOps is a package maintainers Swiss Army knife. It's not an AUR helper, but it's made to help you maintain PKGBUILD files.
- Upstream updates check
- Applying update to a PKGBUILD file
- Availability as GitHub Action
- AUR package maintenance (generate
.SRCINFO, commit, subtree or regular push) - Repo maintenance (build, sign, add to a repo db, upload)
- Usable locally
- Supports only debian repositories as upsteam, example (with only one package and different version)
- Builds locally or in a user-provided chroot
- Commits updates with a commit message generate from a template
- Updates a local system or a chroot
- Somewhat runnable in Docker
Take part! We have discussions, issues and PRs.
Should be available as
- AUR package
- binary package in ejiek's repository
- Cargo package
- Docker image
PacOps docker image is based on archlinux:base-devel and uses itself as a build environment.
docker run -v ${PWD}:/usr/share/pacops pacops ${path_to_a_PKGBUILD}
Git variables:
GIT_AUTHOR_NAME
GIT_AUTHOR_EMAIL
Makepkg variables:
PACKAGER="John Doe <john@doe.com>"
- Documentation
- GitHub as an upstream:
- releases
- tags
- branches
- Rootless containers (currently we don't have a workflow for rootless podman)
- Migrate from dummy parsing to NomCup
- Clean chroot life cycle (create, update, delete)
- Navigate user through repo creation
- State awareness - what's in git, AUR, repo
- Guzuta - Custom repository manager
- repology - Monitors updates
- Chaotic AUR - builds packages from AUR