Difference between revisions of "Arch User Repository/pt-br"
Views
Actions
Namespaces
Variants
Tools
MatrixUser (talk | contribs) (Created page with "====Manual==== Para fazer isso, siga as etapas abaixo: * Certifique-se de ter os arquivos necessários para criar aplicativos a partir do código-fonte") |
Mbatista2006 (talk | contribs) (Created page with "* Várias versões dos mesmos pacotes. * Pacotes desatualizados. * Pacotes quebrados ou funcionando apenas parcialmente. * Pacotes configurados incorretamente que baixam depen...") |
||
Line 17: | Line 17: | ||
Possíveis riscos ao usar pacotes AUR: | Possíveis riscos ao usar pacotes AUR: | ||
* Várias versões dos mesmos pacotes. | |||
* | * Pacotes desatualizados. | ||
* | * Pacotes quebrados ou funcionando apenas parcialmente. | ||
* | * Pacotes configurados incorretamente que baixam dependências desnecessárias, ou não baixam as dependências necessárias, ou ambos. | ||
* | * Pacotes maliciosos (embora extremamente raros). | ||
* | |||
Como tal, embora muitos dos pacotes de software fornecidos pelo AUR devam funcionar, não espere que o processo de instalação seja sempre tão simples como quando está a usar os repositórios oficiais do Manjaro. | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | <div lang="en" dir="ltr" class="mw-content-ltr"> |
Latest revision as of 14:48, 26 September 2024
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.
Possíveis riscos ao usar pacotes AUR:
- Várias versões dos mesmos pacotes.
- Pacotes desatualizados.
- Pacotes quebrados ou funcionando apenas parcialmente.
- Pacotes configurados incorretamente que baixam dependências desnecessárias, ou não baixam as dependências necessárias, ou ambos.
- Pacotes maliciosos (embora extremamente raros).
Como tal, embora muitos dos pacotes de software fornecidos pelo AUR devam funcionar, não espere que o processo de instalação seja sempre tão simples como quando está a usar os repositórios oficiais do Manjaro.
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
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:
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
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
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
Para fazer isso, siga as etapas abaixo:
- Certifique-se de ter os arquivos necessários para criar aplicativos a partir do código-fonte
- Clone the PKGBUILD
- Change directory to cloned folder
- To make/compile the package, run:
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
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
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:
Note: To combine above steps into one:
Atualizando os pacotes instalados do AUR
O seguinte comando irá atualizar todos pacotes no sistema, incluindo compilações AUR
Veja também
Categoria:Página de Conteúdo/pt-br Categoria:Gerenciamento de Software/pt-br