Arch User Repository/de

Overview

Use the AUR at your own risk!

---

No support will be provided by the Manjaro team for any issues that may arise relating to software installations from the AUR. When Manjaro is updated, AUR packages might stop working. This is not a Manjaro issue

Although Manjaro is very close to Arch Linux and mostly compatible —being based on Arch Linux itself— it is not possible to access their official repositories for use in Manjaro. Instead, Manjaro uses its own repositories in order to ensure that any software packages that are accessible, such as system updates and applications, have been fully tested to be compatible and stable before release. It is still possible to access additional software packages from the Arch User Repository (AUR).

Das AUR wird von der Arch Linux-Benutzergemeinschaft selbst verwaltet. Obwohl dieses Repository inoffiziell ist, können Softwarepakete, die zuerst hier platziert wurden, schließlich in das offizielle (Community-)Repository von Arch Linux gelangen, wenn sie populär genug werden.

'AUR, als von der Community gepflegtes Repository, birgt potenzielle Risiken und Probleme.'

Mögliche Risiken bei der Verwendung von AUR-Paketen:

• Mehrere Versionen der gleichen Pakete
• Veraltete Pakete
• Beschädigte oder nur teilweise funktionierende Pakete
• Falsch konfigurierte Pakete, die unnötige Abhängigkeiten herunterladen oder notwendige Abhängigkeiten nicht herunterladen oder beides.
• Bösartige Pakete (wenn auch extrem selten).

Obwohl viele der vom AUR bereitgestellten Softwarepakete funktionieren werden, sollten Sie nicht erwarten, dass der Installationsprozess immer so einfach ist wie bei der Verwendung der offiziellen Manjaro-Repositorys.

On occasion, it may be necessary to manually identify and install dependencies yourself (such as, after an aborted installation attempt).

Again, there is no guarantee that any installed software will work properly, if at all.

Accessing the AUR

Using GUI Pamac

Open Pamac - the name in menu is Add/Remove Software and navigate to the Preferences page. You will be required to enter your password to access it.At Preferences page → select the Third Party tab → and move the slider to enable AUR support.Be sure you have the necessary files for building applications from source

user $ pamac install base-devel git COPY TO CLIPBOARD

Using commandline Pamac

Info

---

It is strongly recommended to follow this link AUR website and examine the relevant page(s) for any and all software intended to be installed.

These pages contain comments from both existing users and package developers, which may provide valuable information (such as, warnings and/or solutions to problems). To search for and install software packages from the AUR, the syntax is:

user $ pamac search -a [software package name] COPY TO CLIPBOARD

For example, if wishing to install Google Chrome - first follow this link to all Google Chrome build scripts and verify which package you want to build.Or you can ask pamac - for Google Chrome candidates. Just use the search command and Google Chrome as the query. Look over the results or narrow the search parameters - just remember pamac cannot tell you of any issues with build scripts - only the relevant page. E.g. following this link to the buildscript for Google Chrome

user $ pamac search Google Chrome COPY TO CLIPBOARD

In the example we choose the standard version of Google Chrome. To build the google-chrome package with pamac enter the following and press enter

user $ pamac build google-chrome COPY TO CLIPBOARD

You will be presented with the outcome of the chosen build with all dependencies and you will be asked a couple of questions.

1. Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
2. Query to continue download and install dependencies then download the sources, build and install the app.
3. You will be asked for your password before anything happens.

Using GUI Octopi

See this guide for enabling AUR support in Octopi.

Installing from the AUR by hand

Manual

To do that follow the steps given below:

• Be sure you have the necessary files for building applications from source

user $ pamac install base-devel git COPY TO CLIPBOARD

• Clone the PKGBUILD

user $ git clone https://aur.archlinux.org/google-chrome.git COPY TO CLIPBOARD

• Change directory to cloned folder

user $ cd google-chrome COPY TO CLIPBOARD

• To make/compile the package, run:

user $ makepkg -s COPY TO CLIPBOARD

This will build the package and pull in any dependencies needed. Note: it won't pull a dependency from the AUR, only from the Manjaro Repos.. If you list the folder content

user $ ls COPY TO CLIPBOARD

you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.zst

• The final event is running $sudo pacman -U on that file

user $ sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst COPY TO CLIPBOARD

And you've done it...the safest way to install from the AUR. This is essentially what most install scripts do for you.

Note: Instead of using sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst can also use:

user $ makepkg -i COPY TO CLIPBOARD

Note: To combine above steps into one:

user $ makepkg -is COPY TO CLIPBOARD

Upgrading the packages installed from the AUR

The following command will upgrade all packages on the system including AUR builds

user $ pamac upgrade -a COPY TO CLIPBOARD

See Also

• Pacman
• Pacman Tips