Difference between revisions of "Arch User Repository"

Latest revision as of 18:05, 29 December 2022

Other languages:

Deutsch • ‎English • ‎Türkçe • ‎français • ‎português do Brasil • ‎русский • ‎فارسی • ‎中文（中国大陆）‎

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).

The AUR is managed by the Arch Linux user community itself. Although this repository is unofficial, software packages first placed here can eventually make their way into Arch Linux's official (community) repository if they become popular enough.

AUR, as a community maintained repository, present potential risks and problems.

Possible risks using AUR packages:

Multiple versions of the same packages.
Out of date packages.
Broken or only partially working packages.
Improperly configured packages which download unnecessary dependencies, or do not download necessary dependencies, or both.
Malicious packages (although extremely rare).

As such, although much of the software packages provided by the AUR should work, do not expect the installation process to always be quite as straight-forward as when you are using the official Manjaro repositories.

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.

Info

You should become familiar with the manual build process in order to be prepared to troubleshoot problems.

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.

Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
Query to continue download and install dependencies then download the sources, build and install the app.
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

@@ Line 1: / Line 1: @@
-= Overview =
+<languages/>
+__TOC__
+<translate>
+==Overview== <!--T:42-->
+{{BoxWarning|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 &mdash;being based on Arch Linux itself&mdash; 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 ''[https://wiki.archlinux.org/index.php/AUR Arch User Repository]'' (AUR).
-{{warning| '''Use the AUR at your own risk!''' Support will not be provided by the Manjaro team for any issues that may arise relating software installations from the AUR. }}
+<!--T:43-->
+The AUR is managed by the Arch Linux user community itself. Although this repository is unofficial, software packages first placed here can eventually make their way into Arch Linux's official (community) repository if they become popular enough.
-Although Manjaro is 100% Arch compatible - being based on Arch itself - it is not possible access the official repositories of the Arch System to download software. Manjaro instead uses its own official repositories in order to ensure that any software packages provided (e.g. system updates and applications) have been fully tested and are completely stable before release.
+<!--T:44-->
+'''AUR, as a community maintained repository, present potential risks and problems.'''
-However, it is still possible to access additional software packages from the ''Arch User Repository'' (AUR), which is managed by the Arch community (i.e. users) themselves. Although this repository is unofficial, software packages first placed here are known to make their way into Arch's official repositories if they become popular enough. '''Unfortunately, as a community maintained repository, using the AUR does still present potential risks and problems.''' These include the AUR providing:
+<!--T:45-->
+Possible risks using AUR packages:
-* Multiple versions of the same packages
+<!--T:46-->
-* Out of date packages
+* Multiple versions of the same packages.
-* Broken or only partially working packages
+* Out of date packages.
-* Improperly configured packages (e.g. downloading unnecessary dependencies, and/or not downloading necessary dependencies)
+* Broken or only partially working packages.
-* Malicious packages (although extremely rare)
+* Improperly configured packages which download unnecessary dependencies, or do not download necessary dependencies, or both.
+* Malicious packages (although extremely rare).
-As such, although much (if not most) of the software packages provided by the AUR should work, do not expect the installation process to always be quite as straightforward as when using the official repositories. On occasion, it may be necessary to manually identify and install dependencies yourself after an aborted installation, for example. In addition, there is no guarantee that any installed software will work properly, if at all.
+<!--T:47-->
+As such, although much of the software packages provided by the AUR should work, do not expect the installation process to always be quite as straight-forward as when you are using the official Manjaro repositories.
+<!--T:48-->
+On occasion, it may be necessary to manually identify and install dependencies yourself (such as, after an aborted installation attempt).
-= Accessing the AUR =
+<!--T:49-->
+'''Again, there is no guarantee that any installed software will work properly, if at all.'''
-Two packages are required in order to access the AUR, which can be installed in the terminal:
+<!--T:63-->
+{{Important|You should become familiar with the manual build process in order to be prepared to troubleshoot problems.}}
-'''1. The base-developer group package:''' Rather than downloading pre-compiled software packages for installation, you will instead be downloading the instructions to build and compile them on your system. This group package is therefore required to do this. '''This should be pre-installed on Manjaro 0.8.1 onwards.'''
+==Accessing the AUR== <!--T:50-->
+===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 &rarr; select the Third Party tab &rarr; and move the slider to enable AUR support. Be sure you have the necessary files for building applications from source
+{{UserCmd|command=pamac install base-devel git}}
-'''2. Either yaourt or packer:''' Either of these are used to search and download from the AUR, rather like pacman is used to search and download from from Manjaro's official repositories. Both will also automatically find and download the necessary dependencies for downloads as well (provided the software packages to be installed properly state which dependencies are needed). Which you may chose is entirely down to personal preference. However, yaourt (an acronym for '''Y'''et '''A'''n'''O'''ther '''U'''ser '''R'''espository '''T'''ool) seems to be the most popular choice, perhaps due to providing additional visual features.
+===Using commandline [[Pamac]]=== <!--T:51-->
+{{Important|It is '''strongly''' recommended to follow this link [https://aur.archlinux.org/ 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:
+{{UserCmd|command=pamac search -a [software package name]}}
-{{note| Although the base developer group package should already be installed on your system, it will be included in the installation instructions anyway. The worst that can happen is that it will be updated!}}
+<!--T:52-->
+For example, if wishing to install ''Google Chrome'' - first follow this link to '''[https://aur.archlinux.org/packages/?K=google-chrome 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 '''[https://aur.archlinux.org/packages/google-chrome buildscript for Google Chrome]'''
+{{UserCmd|command=pamac search Google Chrome}}
-* To install the base developer group package and '''yaourt''', enter the command:
+<!--T:53-->
- sudo pacman -S base-devel yaourt
+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
+{{UserCmd|command=pamac build google-chrome}}
-* To install the base developer group package and '''packer''', enter the command:
+<!--T:54-->
- sudo pacman -S base-devel packer
+You will be presented with the outcome of the chosen build with all dependencies and you will be asked a couple of questions.
+# Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
+# Query to continue download and install dependencies then download the sources, build and install the app.
+# You will be asked for your password before anything happens.
-Once entered, simply follow the (simple) on-screen prompts to complete the installation process.
+===Using GUI [[Octopi]]=== <!--T:55-->
+See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi.
-= Searching for and Installing Software From the AUR =
+===Installing from the AUR by hand=== <!--T:56-->
+====Manual==== <!--T:57-->
+To do that follow the steps given below:
+* Be sure you have the necessary files for building applications from source
+<!--T:58-->
+{{UserCmd|command=pamac install base-devel git}}
+* Clone the PKGBUILD
+{{UserCmd|command=git clone <nowiki>https://aur.archlinux.org/google-chrome.git</nowiki>}}
+* Change directory to cloned folder
+{{UserCmd|command=cd google-chrome}}
+* To make/compile the package, run:
+{{UserCmd|command=makepkg -s}}
+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
+{{UserCmd|command=ls}}
+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
+{{UserCmd|command=sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst}}
+And you've done it...the safest way to install from the AUR. This is essentially what most install scripts do for you.
+<!--T:59-->
+''Note:'' Instead of using ''sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst'' can also use:
+{{UserCmd|command=makepkg -i}}
+''Note:'' To combine above steps into one:
+{{UserCmd|command=makepkg -is}}
+===Upgrading the packages installed from the AUR=== <!--T:60-->
+The following command will upgrade '''all''' packages on the system including AUR builds
+{{UserCmd|command=pamac upgrade -a}}
+==See Also== <!--T:61-->
+* [https://forum.manjaro.org/t/need-to-know-about-manjaro-and-aur/103617 Need to know about Manjaro and AUR]
+* [http://wiki.manjaro.org/index.php?title=Pacman Pacman]
+<!--T:62-->
+[[Category:Contents Page{{#translation:}}]]
+[[Category:Software Management{{#translation:}}]]
+</translate>