Difference between revisions of "Arch User Repository"
From Manjaro
m (fix spelling and sentence) |
m (del Pacman tips) |
||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
__TOC__ | __TOC__ | ||
<translate> | <translate> | ||
<!--T: | ==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. When Manjaro is updated, AUR packages might stop working. '''This is not a Manjaro issue''' | {{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 —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 ''[https://wiki.archlinux.org/index.php/AUR Arch User Repository]'' (AUR). | |||
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 ''[https://wiki.archlinux.org/index.php/AUR Arch User Repository]'' (AUR). | |||
<!--T: | <!--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: | <!--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: | <!--T:45--> | ||
Possible risks using AUR packages: | Possible risks using AUR packages: | ||
<!--T: | <!--T:46--> | ||
* Multiple versions of the same packages. | * Multiple versions of the same packages. | ||
* Out of date packages. | * Out of date packages. | ||
| Line 34: | Line 22: | ||
* Malicious packages (although extremely rare). | * Malicious packages (although extremely rare). | ||
<!--T:47--> | |||
<!--T: | |||
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: | <!--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: | <!--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.''' | ||
<!--T:63--> | |||
{{Important|You should become familiar with the manual build process in order to be prepared to troubleshoot problems.}} | |||
{{ | |||
<!--T: | ==Accessing the AUR== <!--T:50--> | ||
At Preferences page → select the | ===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 | |||
{{UserCmd|command=pamac install base-devel git}} | |||
{{ | |||
<!--T: | ===Using commandline [[Pamac]]=== <!--T:51--> | ||
To search for and install software packages from the AUR, the syntax is: | {{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]}} | {{UserCmd|command=pamac search -a [software package name]}} | ||
<!--T: | <!--T:52--> | ||
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. | 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}} | {{UserCmd|command=pamac search Google Chrome}} | ||
<!--T: | <!--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 | 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}} | {{UserCmd|command=pamac build google-chrome}} | ||
<!--T: | <!--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 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. | # 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. | # You will be asked for your password before anything happens. | ||
===Using GUI [[Octopi]]=== <!--T:55--> | |||
See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi. | |||
<!--T: | |||
See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi.< | ===Installing from the AUR by hand=== <!--T:56--> | ||
====Manual==== <!--T:57--> | |||
<!--T: | |||
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 | ||
< | |||
<!--T:58--> | |||
{{UserCmd|command=pamac install base-devel git}} | {{UserCmd|command=pamac install base-devel git}} | ||
* Clone the PKGBUILD | * Clone the PKGBUILD | ||
{{UserCmd|command=git clone <nowiki>https://aur.archlinux.org/google-chrome.git</nowiki>}} | {{UserCmd|command=git clone <nowiki>https://aur.archlinux.org/google-chrome.git</nowiki>}} | ||
* Change directory to cloned folder | * Change directory to cloned folder | ||
{{UserCmd|command=cd google-chrome}} | {{UserCmd|command=cd google-chrome}} | ||
* To make/compile the package, run: | * To make/compile the package, run: | ||
{{UserCmd|command=makepkg -s}} | {{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 | 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}} | {{UserCmd|command=ls}} | ||
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.zst | 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 | * 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}} | {{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. | And you've done it...the safest way to install from the AUR. This is essentially what most install scripts do for you. | ||
<!--T: | <!--T:59--> | ||
''Note:'' Instead of using ''sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst'' can also use: | ''Note:'' Instead of using ''sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst'' can also use: | ||
{{UserCmd|command=makepkg -i}} | {{UserCmd|command=makepkg -i}} | ||
''Note:'' To combine above steps into one: | ''Note:'' To combine above steps into one: | ||
{{UserCmd|command=makepkg -is}} | |||
{{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}} | {{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] | * [http://wiki.manjaro.org/index.php?title=Pacman Pacman] | ||
<!--T:62--> | |||
[[Category:Contents Page{{#translation:}}]] | [[Category:Contents Page{{#translation:}}]] | ||
[[Category:Software Management{{#translation:}}]] | [[Category:Software Management{{#translation:}}]] | ||
</translate> | |||
Latest revision as of 18:05, 29 December 2022
Overview
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.
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
Using commandline Pamac
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]
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
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
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
- Clone the PKGBUILD
user $ git clone https://aur.archlinux.org/google-chrome.git
- Change directory to cloned folder
user $ cd google-chrome
- To make/compile the package, run:
user $ 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
user $ 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
user $ 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.
Note: Instead of using sudo pacman -U google-chrome-ver.rel.bugfix.build-pkgrel.pkg.zst can also use:
user $ makepkg -i
Note: To combine above steps into one:
user $ makepkg -is
Upgrading the packages installed from the AUR
The following command will upgrade all packages on the system including AUR builds
user $ pamac upgrade -a