SYNOPSIS
aurutils is a collection of scripts to automate usage of the Arch User Repository, with different tasks such as package searching, update checks, or computing dependencies kept separate.
The chosen approach for managing packages is local pacman
repositories, rather than foreign (installed by pacman -U)
packages.
INSTALLATION
Install one of the following packages:
aurutilsfor the release version (recommended).aurutils-gitfor the master branch.
Upgrade notices are posted to the Arch forums. (RSS)
SIGNATURES
Release archives are signed with signify with the following public keys:
RWQawitEue1JU2SxUyRD8LXP8m36QsbaHOkKfvZBfhj00EXBYiDZilp0for2.3.x;RWQcfDbvctqX5i5yNDNqu607LC7mKArHMsq7ziT8ynx9bQwj5m5ZpMJYfor3.0.x;RWSiKm8qeKjPfppkN7lm/N4qENa3Racl7DRMfWK4JQS7bl2i/NuI3ZZGfor3.1.x;
The above keys are also published on ArchWiki.
A release archive can be verified with the following command:
signify -V -p aurutils.pub -m <version>.tar.gz
USAGE
Documentation is included as groff manuals. aur(1) contains a
general overview, instructions on creating a local repository, and
several examples.
VERSIONING
| Code changes | |
|---|---|
| Major changes | Result in a bump of major version (x.0.0). Upgrades to a new major version may require a rewrite of interfacing software, or significant changes in workflow. |
| Minor changes (incompatible) | Result in a bump of minor version (x.y.0). Typically used when application names or command-line options change in a minor way. |
| Minor changes (compatible) | Result in a bump of maintenance version (x.y.z). Typically used for bug fixes or new, compatible features. |
TROUBLESHOOTING
See ISSUE_TEMPLATE.md. For informal discussion, see the
#aurutils channel on freenode.
