This document outlines the process for Arch Linux package maintainers to add new packages to the official repositories.
- Browse the community Trusted User Repository located at http://aur.archlinux.org/packages.php?L=3
- Once you have identified the packages you wish to adopt, send an email message to firstname.lastname@example.org notifying the Trusted Users (TUs) and other AL package maintainers of the packages you want to adopt. NOTE: You should also sign up on the email@example.com mailing list.
- Retreive the PKGBUILDs for the new packages:
and perform the testing/verificatoin on the PKGBUILD. Note that there is no need to change the version number unless changes are made to the package, this will minimize needless re-downloading.
- When you are ready to add it to the official AL repos, follow the guidelines specified in http://www.archlinux.org/devel/pkgmaint_guide.txt. After adding it to the AL repos, send another email to firstname.lastname@example.org asking the TUs to remove the original package from the **community** repo.
- Don't forget to adopt the packages under /devel because they'll initially show up as orphans.
The BIG Picture
Generally speaking, new packages are submitted by AL's end users to the AUR's **unsupported** collection on http://aur.archlinux.org/. From there, one of the TUs will take the package, test the PKGBUILD locally, fix any errors and make sure it conforms to AL package guidelines. When the TU has finished testing it, they will place the package in the **community** repo at ftp://ftp.archlinux.org/community/
When the package has been placed in the **community** repo, AL users have access to the package via Template:Pacman (assuming the user has enabled the **community** repo in their /etc/pacman.conf file). Once the package has lived in the **community** repo for a while bug-free, then an AL package maintainer can elect to adopt the package and follow the procedure outlined above.
Trusted Users are selected users within the AL user community that show sound Linux knowledge and the ability to produce solid PKGBUILDs. The **community** repo is not officially supported by AL developers/package maintainers. The TUs are fully responsible for the packages found within it. It is not until a package is adopted into the main AL repos that the AL team becomes responsible for the package.