Because the AUR is a pretty low quality repo. Not sure if anything has changed since 2 years ago, but last I used arch, the AUR was full of broken, abandoned, and unbuildable packages. The Debian repos, fedora+rpmfusion, etc, provide a comparable number of software packages with substantially higher quality, hence no need for the AUR. Fedora actually has COPRs which suffer from the same quality issues as the AUR for similar reasons.
Thing is, the AUR isn’t really meant to be your primary repo. You can really get anything into the AUR.
The reason why I love it so much is because if I need a package that’s not in the main arch repo (which tbh isn’t many), then I don’t need to bother going to some github page and compiling from source, I can just find it in the AUR and it’s all done for me. I did this with things like goverlay and it’s one thing that I immediately miss when I distro hop away from something arch-based.
NixOS has NUR, but it’s not necessary because they take everyone’s pull requests in the official repo. I’ve been maintaining the software I use myself on the official nixpkgs, so I don’t need to use the NUR.
The majority of other distros value package managers that allow for complex graph evaluation of dependencies, and the ability to roll back. This is granted with rpm and Deb, but not for pkgsource, which is a pretty lightweight format compared to those.
As for AUR, the major distros (Ubuntu, Debian, Fedora) support 3p repositories as well. The main concern is security. IIRC one of major complaints for AUR in the past was that it didn’t foresee a strongly secure distribution system.
It gives you a lot of convenience, auto updates, and dependencies. While it is nice being up to date by checking the git and making it by yourself it is much more convenient to have a package manager for it when you have many Make packages
when it’s the main reason why so many people use Arch Linux?
AUR is one reason why I use Arch. But not the reason. Besides AUR, Arch has many other advantages from my point of view. Like for example the wiki that also users of other distributions use. Or the many vanilla packages. Or that you can easily create your own packages through the PKGBUILD files. Or that, based on my own experience, Arch is quite problem-free to use despite the current packages.
One reason why other distributions don’t have something like AUR could be that AUR is not an official offering, so no verification is done in advance either. Thus, it has happened at least once that someone has manipulated PKGBUILD files in bad faith (lists.archlinux.org/pipermail/…/034151.html). The Wiki does not warn against the use for nothing.
However, it is much easier for the user to check the files in the AUR in advance than it is, for example, with ready-made packages in an unofficial PPA.
Arch has many other advantages from my point of view. Like for example the wiki that also users of other distributions use.
I remember when started using #! and then Debian with Openbox. It didn’t matter what problem I had, the answer and solution were always in the Arch Wiki.
openSUSE has OBS, Fedora has COPR, and I’m pretty sure both Gentoo and NixOS have similar stuff. Do Ubuntu’s PPAs count? Flatpaks and AppImages are also similar, although they are more limited and they aren’t exactly “standard” packages.
OBS and COPR don’t even come close to the AUR in terms of ease of use. AUR is one searchable index, OBS and COPR are more like separate repositories that you have to find and add manually. There’s multiple people building the same packages and you have to figure out which one you want to rely on. You also can’t easily edit the packaging instructions and rebuild a package if it doesn’t work for you.
PPAs are fundamentally flawed. Since each repository is separate, they only care to maintain consistency internally, plus the packages of the Ubuntu version they were based on.
Adding a PPA and using its packages on your system takes your dependency tree into a “cul de sac” where only that PPA is reliable.
But of course people use multiple PPAs so what happens is that the dependency tree grows increasingly unrecoverable.
Eventually you get the dreaded “requires X but cannot be installed” errors which pretty much mean you’ve hit a dead end. You can recover your system from it (aptitude can provide solutions) but they are extremely invasive, basically come down to uninstalling and reinstalling thousands of packages to bring your tree back to a manageable state.
I admit I haven’t used Ubuntu in years, so I didn’t think they were that bad. Thanks for the info, it made me learn a dependency hell scenario I never thought about before.
Debian technically has the same issue but people who want Debian usually stick to stable + backports so it’s less frequent.
Yeah that’s why distributions which put all their community packages in one place with the same dependencies are more resilient in this respect.
Arch’s AUR is not perfect either, you can have packages that list dependencies badly or replace core packages so you can still mess up but in a different way.
NixOS seems to have hit on a very robust formula that lets packages coexist with minimal friction.
I wanted to use the up to date version of FFMPEG, had to download the binary from the website. Wanted to install some program that needed the latest version of KDE, had to install a PPA which updated a LOT of packages and at the end it would break many other apps installed from other PPAs.
At some point I realized using Arch was just much less work than worrying myself about all the dependencies that could break when you don’t stick to what’s available in their official repositories.
Probably for the same reasons why there are so many packaging formats in the first place. If everyone settled on deb, rpm, or arch style tar packages. Then we wouldn’t need the aur, flatpak, snap, appimage or anything else.
Don’t know. The AUR is a big reason I use Arch. Obviously there’s PPAs/OBS or whatever but they’re not implemented nearly as well, I don’t need to go searching for new repos with the AUR or messing with repo priorities (fun times on Suse…) since everything is in the one place and there’s procedures for taking over orphaned packages. I use about twenty or so packages from it, many of them not packaged for any other distro. Personally not interested in using Flatpak since two package management systems is not my idea of KISS. Poor man’s AUR imo :).
For my needs I found that that flatpak just werks for anything not on the distros repos. And for the really obscure stuff I’ve used, I could just build from source
Having to build from source is exactly why I don’t think the AUR has a replacement. There are many similar package managers but non as extensive. Like NUR for NixOS.
Your sample rate is 55 people on lemmy. DistroWatch has more than tripple the amount of arch users hitting the page per day. There are about 5500 registered accounts on the official arch forum.
AUR is really not that great? Who moves to Arch for it? It’s been my main OS for I don’t even know how long but AUR has been my primary pain point. PKGBUILD is cool and useful useful. AUR however, is untrusted (or rather shouldn’t be trusted), often out of date, sometimes requires compilation, and doesn’t even have any good pacman wrappers since yaourt (that I’m aware of).
It is technically possible to install paru through Cargo which you can get just from pacman by installing rust and you can install pikaur through PIP. Both can mess with your systems packages though so I do not recommend it.
Yeah, AUR isn't great because it's engineered as a second class citizen given the necessity of third-party tools like yaourt, and that the whole process of installation can't be done directly through the first-party tool (pacman), such that updating the main packages can trivially cause third-party packages to suddenly stop working. ArchLinux offers just one way - their way - when it comes to dealing with software versions and if the user happens to depend on some thing they want to keep around, tough luck, and hope that future upgrades don't force a breakage that requires a recompilation which may no longer work.
That runs completely opposite to Gentoo, where the first-party repositories are defined the exact same way as third-party repositories, and that updates to first-party libraries generally don't immediately break existing binaries because the distribution was built with recompilation requirements from upgrade breakages in mind. Since third-party packages are treated no differently (no second class citizen treatment), their first-party tool (emerge) can manage the complete lifecycle of "third-party" packages in the exact same manner (as opposed to needing any third party tools to manage the build). This alone reduces the mental bandwidth for the end-users that are managing their set of required packages for their systems. All this flexibility is ultimately part of the various reasons that got me to switch from Arch back to Gentoo.
AUR however, is untrusted (or rather shouldn’t be trusted), often out of date
So basically like a PPA which are used by many users of Ubuntu. The only difference is that the PKBUILD files used to build the packages are easier to check than the final packages in a PPA. And that’s exactly what is a big advantage for me.
sometimes requires compilation,
This is often because a project does not offer ready-made packages that can be downloaded from Github, for example. There are also people who do not trust ready-made packages from unknown third parties. I wouldn’t necessarily download and execute a binary file from a Dropbox of a user I don’t know. Compiling is the safer way if the source code is downloaded from a more trustworthy source.
and doesn’t even have any good pacman wrappers since yaourt (that I’m aware of).
Personally, I don’t think aurutils, paru and yay are bad. I currently use aurutils myself. But as far as AUR helpers are concerned, everyone has their own preferences. That’s why there are so many ;-)
I’ve been on NixOS for about a week now and I can say I’ve got access to pretty much all of the packages I was using on Arch just from nixpkgs. I even found it quite easy to package stuff myself!
I am only using them and they seem very kino. I don’t do anything complex with them, but, I like that adding new repos is as simple as reponame.url = repourl and then you can use its stuff after adding it to your outputs