@hawthornbunny@equestria.social
2026-06-24 12:08 UTC
Replies (1)
-
@Karcsesz@equestria.social 2026-06-25 06:51
@hawthornbunny@equestria.social You might be (understandably) conflating some things here. pacman has zero idea about the AUR on its own. Arch has three binary package sources grouped by how important the packages are: core (must-haves, like the kernel), extra (nice-to-haves, like desktop applications), and multilib for allowing a 32 bit programs on 64 bit kernels. Then there is the AUR that only provides glorified shell scripts that build a given package from source. Officially you have to git clone the script, run makepkg on it, then tell pacman to install the resulting package file. Now the part where it gets confusing: AUR helpers. Programs like pamac, paru, or yay take pacman's package management workflow and bolt on features that enable the user to install AUR packages (usually signified with AUR/pkgname) as if they were prebuilt packages. The helper grabs the script, builds, installs, and the only difference is you get a prompt to audit the script before building that you can too easily skip.