Manjaro Difference between revisions of "Arch User Repository"

Difference between revisions of "Arch User Repository"

From Manjaro
imported>Fhdk
(major rewrite to clarify Pamac activation of AUR and using only pamac as AUR helper)
m (del Pacman tips)
 
(24 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= Overview =
<languages/>
 
__TOC__
{{warning|'''Use the AUR at your own risk!'''
<translate>
 
==Overview== <!--T:42-->
'''No support''' will be provided by the Manjaro team for any issues that may arise relating to software installations from the AUR.
{{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).  
With Manjaro updates, 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).  


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


<!--T:44-->
'''AUR, as a community maintained repository, present potential risks and problems.'''  
'''AUR, as a community maintained repository, present potential risks and problems.'''  


<!--T:45-->
Possible risks using AUR packages:
Possible risks using AUR packages:


<!--T:46-->
* Multiple versions of the same packages.
* Multiple versions of the same packages.
* Out of date packages.
* Out of date packages.
Line 25: Line 22:
* Malicious packages (although extremely rare).
* Malicious packages (although extremely rare).


 
<!--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.  
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).  
On occasion, it may be necessary to manually identify and install dependencies yourself (such as, after an aborted installation attempt).  


<!--T:49-->
'''Again, there is no guarantee that any installed software will work properly, if at all.'''
'''Again, there is no guarantee that any installed software will work properly, if at all.'''


= Accessing the AUR =
<!--T:63-->
 
{{Important|You should become familiar with the manual build process in order to be prepared to troubleshoot problems.}}
1. Pamac GUI: graphical application '''Add/Remove Software''' application named '''Pamac'''.
 
2. Pamac CLI: command line tool '''pamac build aur-pkg-name'''.
 
(<u>Note for Octopi users</u>: Octopi can only use ''trizen'' or ''yaourt'' to access 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 &rarr; seleetc the AUR tab &rarr; and move the slider to enable AUR.
 
'''To access AUR from [[Octopi]]'':
You need to turn it on in Tools &rarr; Options &rarr; AUR. Then [[Octopi]] will include the green alien head. Click on it, enter your search term, and hit enter to search the AUR.
 
== Using commandline [[Pamac]] ==
 
{{tip|It is '''strongly''' recommended to first visit the [http://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).
 
The AUR website can be found '''[http://aur.archlinux.org/ here]'''}}


Yay must be used in the terminal and is itself very similar to pacman to use; furthermore, as with pacman, it is not necessary to specify precise or complete package names in order to search for or download software. To search for and install software packages from the AUR, the syntax is:
==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}}


pamac search -a [software package name]
===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]}}


For example, if wishing to install ''Visual Studio Code'' AUR version (a popular source code editor) enter ''visual studio'' as the query and a list of potential matches is shown. To build the example with '''pamac''' enter the following and press enter
<!--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}}


pamac build visual-studio-code-bin
<!--T:53-->
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}}


<!--T:54-->
You will be presented with the outcome of the chosen build with all dependencies and you will be asked a couple of questions.
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.


1. Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
===Using GUI [[Octopi]]=== <!--T:55-->
2. Query to continue download and install dependencies then download the sources, build and install the app.
See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi.


You will be asked for your password before anything happens.
===Installing from the AUR by hand=== <!--T:56-->


<br clear="all" />
====Manual==== <!--T:57-->
 
= Installing from the AUR by hand =
 
== Manual ==
To do that follow the steps given below:
To do that follow the steps given below:
* Be sure you have the necessary files for building applications from source
* Be sure you have the necessary files for building applications from source
pamac install base-devel git
* Download the tarball from the AUR preferably to ''~/Downloads''
(just click on the tarball from your browser and you should get it)
* Make a sub-directory in downloads called builds:
mkdir ~/Downloads/builds
-- Move the tarball to builds (Note that foo is a placeholder for the actual name of the package you've downloaded):
mv foo.tar.gz builds
-- Change directory to the builds folder-
cd builds
-- Untar the tarball
tar -xvf foo.tar.gz
-- Move into the new sub-directory
cd <foo>


<!--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:
* To make/compile the package, run:
makepkg -s
{{UserCmd|command=makepkg -s}}
This will build the package and pull in any dependencies needed.
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
''Note: it won't pull a dependency from the AUR, only from the Manjaro Repos.''
{{UserCmd|command=ls}}
 
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.zst
If you run 
* The final event is running $sudo pacman -U on that file
  ls
{{UserCmd|command=sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst}}
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.xz (usually)
And you've done it...the safest way to install from the AUR. This is essentially what most install scripts do for you.
 
 
* The final event is running $sudo pacman -U on that file-
sudo pacman -U foo.pkg.xz
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 foo.pkg.xz'' can also use:
makepkg -i
 


<!--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:
''Note:'' To combine above steps into one:
makepkg -is  
{{UserCmd|command=makepkg -is}}


You can ask for support for installing by hand at the following link-[http://forum.manjaro.org/index.php?topic=7076.msg61520#msg61520]
(Courtesy bloomode for the tutorial).
= Upgrading the packages installed from the AUR =


===Upgrading the packages installed from the AUR=== <!--T:60-->
The following command will upgrade '''all''' packages on the system including AUR builds
The following command will upgrade '''all''' packages on the system including AUR builds
{{UserCmd|command=pamac upgrade -a}}


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]
= See Also =
* [http://wiki.manjaro.org/index.php?title=Pacman Pacman]
 
 
[http://wiki.manjaro.org/index.php?title=Pacman Pacman]
 
[http://wiki.manjaro.org/index.php?title=Pacman_Tips Pacman Tips]
 
 


[[Category:Contents Page]]
<!--T:62-->
[[Category:Software Management]]
[[Category:Contents Page{{#translation:}}]]
[[Category:Software Management{{#translation:}}]]
</translate>

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.

  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

Retrieved from "https://wiki.manjaro.org/index.php?title=Arch_User_Repository&oldid=39817"
Cookies help us deliver our services. By using our services, you agree to our use of cookies.