Manjaro Difference between revisions of "Arch User Repository"

Difference between revisions of "Arch User Repository"

From Manjaro
(general reformatting and proofreading)
m (vivaldi is now in official repo - replaced with google chrome - using google-chrome as example build for all examples)
Line 44: Line 44:
{{UserCmd|command=pamac search -a [software package name]}}
{{UserCmd|command=pamac search -a [software package name]}}


For example, if wishing to install ''Vivaldi'' enter ''vivaldi'' as the query and a list of potential matches is shown. To build the example with '''pamac''' enter the following and press enter
For example, if wishing to install ''Google Chrome'' enter ''google-chrome'' as the query and a list of potential matches is shown. To build the example with '''pamac''' enter the following and press enter
{{UserCmd|command=pamac build vivaldi}}
{{UserCmd|command=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.
You will be presented with the outcome of the chosen build with all dependencies and you will be asked a couple of questions.
Line 61: Line 61:
{{UserCmd|command=pamac install base-devel git}}
{{UserCmd|command=pamac install base-devel git}}
* Clone the PKGBUILD
* Clone the PKGBUILD
{{UserCmd|command=git clone https://aur.archlinux.org/foo.git}}
{{UserCmd|command=git clone https://aur.archlinux.org/google-chrome.git}}
* Change directory to cloned folder
* Change directory to cloned folder
{{UserCmd|command=cd foo}}
{{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}}
Line 70: Line 70:
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 foo.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.


''Note:'' Instead of using ''sudo pacman -U foo.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}}



Revision as of 06:59, 17 December 2020

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.

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 AUR tab → and move the slider to enable AUR.

Using commandline Pamac

Info
It is strongly recommended to first visit the 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 here


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 enter google-chrome as the query and a list of potential matches is shown. To build the example 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

Cookies help us deliver our services. By using our services, you agree to our use of cookies.