Search Criteria
Package Details: archavenger-git 0.0.3.r0.g869fc9a-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/archavenger-git.git (read-only, click to copy) |
|---|---|
| Package Base: | archavenger-git |
| Description: | Archavenger is a simple tool for cleaning up Arch Linux package repositories. |
| Upstream URL: | https://github.com/kobe-koto/Archavenger |
| Licenses: | MIT |
| Conflicts: | archavenger |
| Provides: | archavenger |
| Submitter: | kobe-koto |
| Maintainer: | kobe-koto |
| Last Packager: | kobe-koto |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2026-04-11 09:29 (UTC) |
| Last Updated: | 2026-04-23 07:38 (UTC) |
Latest Comments
kobe-koto commented on 2026-04-12 01:21 (UTC)
Hi @yochananmarqos, great question. And sorry I didn't make that clear in the README (it’s currently just a copy-paste of the --help output)!
Right now, there is definitely significant overlap with paccache. However, I’m building this to handle lifecycle synchronization for custom repos.
While paccache manages version retention, it doesn’t "know" if a package should be removed from the repo index entirely because it was dropped from the upstream builder (like lilac.yaml-s or my PreAUR configs). I’m aiming for a tool that can perform "Garbage Collection" based on that kinds of external metadata, ensuring the repo stays in sync with the build-config.
TL;DR: It’s basic for now, but the goal is automated repo-db pruning for custom build workflows, and it's my fault that i didn't made that clear in README
also see: https://wiki.archlinuxcn.org/maint/Lilac https://github.com/kobe-koto/PreAUR
yochananmarqos commented on 2026-04-11 20:57 (UTC)
Just curious: what does this do that
paccachedoesn't?