In order to display information in web interface AUR attempts to parse PKGBUILD and salvage package name, version and other information from it.
PKGBUILDs are Bash scripts, and correctly parsing Bash scripts is a huge challenge (which is why makepkg is a Bash script itself: it includes PKGBUILD of package being built via
source directive). AUR metadata files were created to get rid of some hacks, used by AUR package maintainers to work around incorrect parsing. See also FS#25210, FS#15043 and FS#16394.
How it works
By adding a metadata file called ".AURINFO" to source tarballs to overwrite specific PKGBUILD fields.
.AURINFO files are parsed line by line. The syntax for each line is
key = value, where key is any of the following field names:
Multiple "depend" lines can be specified to add multiple dependencies. This format closely matches the
.PKGINFO format that is used for binary packages in pacman/libalpm. It can be extended by field name prefixes or sections to support split packages later.
What does not work
- Split packages
- Multiple architectures (
x86_64dependencies tend to be more numerous, so just put them)
pkgbuild_reflection and mkaurball
pkgbuild_reflection is a set of tools for generating
.AURINFO files. One of the provided tools is
mkaurball, which is a script that runs
makepkg --source, generates an
.AURINFO file, and inserts it into the resulting source package.
mkaurballis a wrapper for
makepkg --source. When creating source packages for inclusion in the AUR, use
mkaurballinstead of running
Install the package AUR from the Arch User Repository.