repo-add [options] <path-to-db> <package|delta> [<package|delta> ...]
repo-remove [options] <path-to-db> <packagename|delta> [<packagename|delta> ...]
repo-add and repo-remove are two scripts to help build a package database for packages built with makepkg(8) and installed with pacman(8). They also handle package deltas produced by pkgdelta(8).
repo-add will update a package database by reading a built package or package delta file. Multiple packages and/or deltas to add can be specified on the command line.
If a matching ".sig" file is found alongside a package file, the signature will automatically be embedded into the database.
repo-remove will update a package database by removing the package name or delta specified on the command line. Multiple packages and/or delta to remove can be specified on the command line.
A package database is a tar file, optionally compressed. Valid extensions are ".db" followed by an archive extension of ".tar", ".tar.gz", ".tar.bz2", ".tar.xz", or ".tar.Z". The file does not need to exist, but all parent directories must exist.
-q, --quiet
-s, --sign
-k, --key <key>
-v, --verify
--nocolor
-d, --delta
-n, --new
-R, --remove
repo-add foo.db.tar.xz <pkg1> [<pkg2> ...]
This creates two separate databases; a smaller database "foo.db.tar.xz" used by pacman and a large database containing package file lists "foo.files.tar.xz" for use by other utilities. While pacman can use the large database (if renamed with a db.tar* extension), there is currently no additional benefit for the larger download.
makepkg(8), pacman(8), pkgdelta(8)
See the pacman website at https://www.archlinux.org/pacman/ for current information on pacman and its related tools.
Bugs? You must be kidding; there are no bugs in this software. But if we happen to be wrong, send us an email with as much detail as possible to pacman-dev@archlinux.org.
Current maintainers:
Past major contributors:
For additional contributors, use git shortlog -s on the pacman.git repository.