Difference between revisions of "Arch User Repository"

m
→‎Overview: Style updates.
imported>Verityproductions
imported>Daemox
m (→‎Overview: Style updates.)
Line 4: Line 4:




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.
Although Manjaro is one-hundred percent Arch Linux 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 (e.g. system updates and applications) have been fully tested and are stable before release.


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:
With that said, it is still possible to access additional software packages from the ''[https://wiki.archlinux.org/index.php/AUR 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 ultimately make their way into Arch Linux's official (community) repository if they become popular enough. '''Unfortunately, as a community maintained repository, using the AUR does still present potential risks and problems.''' Risks, such as, the AUR providing:


* Multiple versions of the same packages
* Multiple versions of the same packages.
* Out of date packages
* Out of date packages.
* Broken or only partially working packages
* Broken or only partially working packages.
* Improperly configured packages (e.g. downloading unnecessary dependencies, and/or not downloading necessary dependencies)
* Improperly configured packages (e.g. downloading unnecessary dependencies, or not downloading necessary dependencies, or both).
* Malicious packages (although extremely rare)  
* 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 straightforward as when using the official repositories. On occasion, it may be necessary to manually identify and install dependencies yourself after an aborted installation attempt, for example. In addition, there is no guarantee that any installed software will work properly, if at all.
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 (e.g. after an aborted installation attempt). Again, there is no guarantee that any installed software will work properly (if at all).
 


= Accessing the AUR =
= Accessing the AUR =
Anonymous user