Difference between revisions of "Arch User Repository"

Arch User Repository (view source)

Revision as of 21:44, 4 September 2021

252 bytes added , 3 years ago

Marked this version for translation

Oguzkagan

Bureaucrats, Interface administrators, Moderators, nuke, Administrators

854

edits

@@ Line 2: / Line 2: @@
 __TOC__
 <translate>
-==Overview==
+==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).
+<!--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.
+<!--T:44-->
 '''AUR, as a community maintained repository, present potential risks and problems.'''
+<!--T:45-->
 Possible risks using AUR packages:
+<!--T:46-->
 * Multiple versions of the same packages.
 * Out of date packages.
@@ Line 18: / Line 22: @@
 * 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.
+<!--T:48-->
 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.'''
-==Accessing the AUR==
+==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}}
-===Using commandline [[Pamac]]===
+===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]}}
+<!--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}}
+<!--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.
 # Query to edit build files. This is a precaution to verify that the build scripts does not contain malicious actions.
@@ Line 46: / Line 56: @@
 # You will be asked for your password before anything happens.
-===Using GUI [[Octopi]]===
+===Using GUI [[Octopi]]=== <!--T:55-->
 See [[Octopi#Accessing_the_AUR|this guide]] for enabling AUR support in Octopi.
-===Installing from the AUR by hand===
+===Installing from the AUR by hand=== <!--T:56-->
-====Manual====
+====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
@@ Line 69: / Line 80: @@
 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}}
@@ Line 75: / Line 87: @@
-===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
 {{UserCmd|command=pamac upgrade -a}}
-==See Also==
+==See Also== <!--T:61-->
 * [http://wiki.manjaro.org/index.php?title=Pacman Pacman]
 * [http://wiki.manjaro.org/index.php?title=Pacman_Tips Pacman Tips]
+<!--T:62-->
 [[Category:Contents Page{{#translation:}}]]
 [[Category:Software Management{{#translation:}}]]
 </translate>