If you have been using Arch Linux or other distributions based on Arch such as Manjaro, you might have comes across the term AUR. You try to install a new software and someone suggests to install it from AUR. This leaves you confused.
What is this AUR? Why is it used? How to use AUR? I’ll answer these questions in this article.
What is AUR?
AUR stands for Arch User Repository. It is a community-driven repository for Arch-based Linux distributions users. It contains package descriptions named PKGBUILDs that allow you to compile a package from source with makepkg and then install it via pacman (package manager in Arch Linux).
The AUR was created to organize and share new packages from the community and to help accelerate popular packages’ inclusion into the community repository.
A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds (PKGBUILD and related files).
The AUR community has the ability to vote for packages in the AUR. If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository directly accessible by pacman.
In short, AUR is the way for developers to make new software available to Arch Linux users before the software is officially included in Arch repositories.
Should you use AUR? What’s the risk involved?
Using the AUR is like crossing the street. If you proceed with caution you should be fine.
If you are new to Linux it is advised to not to use the AUR until you build a foundation knowledge about Arch/Manjaro and Linux in general.
It is true that anyone can upload packages to the AUR but the Trusted Users (TUs) are charged with keeping an eye on what gets uploaded. Although TUs perform quality control to the uploaded packages, there is in no guarantee that packages in the AUR are well formed or not malicious.
In practice the AUR seems to be quite safe but in theory it can do some damage, but only if you are not careful. A smart Arch user, always inspects PKGBUILDs and *.install files when building packages from the AUR.
Additionally TUs (Trusted Users) also remove packages in the AUR that are included in core/extra/community so there should be no naming conflicts between them. The AUR will often contain developmental versions of packages (cvs/svn/git/etc) but they will have modified names such as foo-git.
As for the AUR packages, pacman handles dependency resolution and detects file conflicts so you never have to worry about overwriting files in one package with files from another package unless you use the “–force” option by default. If you do that, you probably have more serious problems than file conflicts.
How to use AUR?
The simplest way to use AUR is through a AUR helper. An AUR helper is a command line tool (some has GUI as well) that lets you search for packages published on the AUR and install them.
Installing an AUR helper on Arch Linux
Let’s say you want to use Yay AUR helper. Make sure that you have git installed on Linux. And then clone the repository, go to the directory and build the package.
Use these commands one by one for that:
sudo pacman -S git
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -siOnce installed, you can use yay command like this to install a package:
yay -S package_nameIt’s not that you must use AUR helper for installing packages from AUR. Expand the next section to see how to use AUR without AUR helper.
Installing AUR packages without AUR helpers
If you don’t want to use AUR helper, you can install packages from AUR on your own as well.
As soon as you find the package you want to install on AUR page it is advised to confirm “Licence”, “Popularity”, “Last Updated”, “Dependencies” and so on as an extra quality control step.
git clone [package URL]
cd [package name]
makepkg -siFor example. let’s say you want to install telegram desktop package:
git clone https://aur.archlinux.org/telegram-desktop-git.git
cd telegram-desktop-git
makepkg -siEnabling AUR support in Manjaro Linux
AUR isn’t enabled by default and you have to enable it through pamac. My laptop runs Manjaro Cinnamon but the steps are same for all Manjaro flavors.
Open Pamac (listed as Add/Remove Software):
Once you are in pamac go to preferences like shown below.
In preferences dialog box go to AUR tab, enable the AUR support, enable check for updates and close the dialog box.
You can now search for packages and those which belong to AUR can be identified by the tag under the package descriptions.
AUR is one of the many reasons why people love Arch Linux and you can see why it is so popular.
I hope you find this article useful and keep an eye on social media for upcoming Arch related topics.
Does not look like my Manjaro (latest download). Delete this or upgrade it.
Two manjaro installs does not have to look the same. Are you also running cinnamon like the writer of the article? I guess not since it is not one of the most downloaded Manjaro DEs.
Hi Dimitrios
The correct command for install yay is:
sudo pacman -S git
git clone https://aur.archlinux.org/yay-git.git
cd yay-git
makepkg -si
git clone must be done without sudo (otherwise you will have permission error when makepkg)
and the directory of yay is yay-git
Hi Testato,
There are three different yay packages to choose, ranked below by popularity. The majority of users find the yay-bin package the fastest to use. Personally I use yay.
https://aur.archlinux.org/packages/yay/
https://aur.archlinux.org/packages/yay-bin/
https://aur.archlinux.org/packages/yay-git/
As for the git clone command, it needs to be executed without sudo indeed.
Ok, but you choosed to use yay-git in your article, so you will not find yay directory but yay-git directory
In your article you should change the “git” line or the “cd” line ;-)
Thanks for spotting the typo:)
last one,
you need install base-devel, on some Arch distro, expecially the minimal, it is not installed.
if you write for newbie you must double-check all. The correct information is one of the biggest problem in linux community, ad if this is not done well “the housewife” will remain on Windows :-)
You neglected to mention the base-devel group is assumed to be installed for using the AUR.
sudo pacman -Syu –needed base-devel
Hi, a full description of makepkg script is already hyperlinked. It can be useful though to separately mention it to ensure the base-devel package group is installed in full, spot-on comment!
“A smart Arch user, always inspects PKGBUILDs and *.install files when building packages from the AUR.”
That is the problem for average/newbie users (who are by some recommended to use Manjaro for some reason) they dont understand what they see when they inspect.