ArchLinux User-community Repository (AUR)
From ArchWiki
| Article summary |
|---|
| Provides an overview of the Arch User Repository. |
| Available in languages |
| English |
| Česky |
| Español |
| Italiano |
| Nederlands |
| 简体中文 |
| Français |
| Links |
| AUR Web Interface |
| AUR Mailing List |
| Guidelines |
| AUR User Guidelines |
| AUR Trusted User Guidelines |
Contents |
Overview
The Arch Linux User-Community Repository (AUR) is a community-driven repository of PKGBUILDS (no binaries) for Arch users. The AUR was initially conceived to organize the sharing of PKGBUILDs amongst the wider community and to expedite the inclusion of popular user-contributed packages into the community repo.
It is called the birthplace of Arch's new packages--in the AUR, the users contribute their own packages. The AUR community votes for or against them, and once a package has been voted high enough, a AUR Trusted User takes it to the [community] repository, which is accessible via pacman and ABS.
Important Documents
Besides this article, please make sure to read the AUR User Guidelines if you want to be an AUR User, and the AUR Trusted User Guidelines if you plan to be a Trusted User.
Getting Started
Users can search and download PKGBUILDs from the AUR Web Interface. These PKGBUILDs can be built into installable packages using makepkg, then installed using pacman.
- Read the AUR_User_Guidelines for more info, including:
- a short tutorial on installing AUR packages
- how to enable the [community] repository in pacman and ABS.
- Visit the AUR Web Interface to inform yourself on updates and happenings. There you will also find statistics and an up-to-date list of newest available packages available in AUR.
- Take a look at the AUR Q & A.
- Finally, be sure you adjust your /etc/Makepkg.conf to make the hardware specs of your processor prior to building your packages from the AUR. A siginificant speed-up in make times can be realized on systems with multi-core processors by adjusting the MAKEFLAGS variable; users can also enable hardware-specific optimizations in gcc via the CFLAGS variable. See the aforementioned wikipage for more.
History
The following items are listed for historical purposes only. They have since been superseded by the AUR and are no longer available.
Incoming
At the beginning, there was:
ftp://ftp.archlinux.org/incoming
and people contributed by simply uploading the PKGBUILD, the needed supplementary files and the built Package itself to the server. The package remained there until a Package Maintainer saw it and adopted it.
Trusted User Repositories
Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).
See Also
- AUR Helpers can help you search, download and install packages from AUR.