The setup is kind of a kind of a logical fallacy here. More people are using Debian and RPM based distributions than Arch Linux. That being said:
Arch Linux has the AUR because at the time it was developed, the standards for distributing software on Linux were either RPM or DEB repositories. AUR was a necessity because one could get software on those distributions from the official vendor, but nobody was supporting Arch Linux. So it was a stopgap, an equalizer for one outlier platform.
It’s hardly the first such repository: FreeBSD ports and NetBSD pkgsrc predate the AUR by over a decade. Slackpkg predates AUR by a couple of years as well, though possibly not slapt-get. Gentoo has portage. Anyway, they took an idea that was already well-established, and catered it to a distribution that had fewer software options than major distributions.
These days it’s still the same scenario: a placeholder, to equalize what’s available for Arch Linux users versus other distributions.
People use Arch because it is a rolling release with a well-documented wiki. AUR is a nice perk, but hardly the main reason that people are using Arch Linux, given that other similar systems have existed for older distributions and operating systems for longer.
I don’t believe the setup is a fallacy, the AUR is one of the main reasons I use Arch. Sure, other distros may have similar systems in place, but the number of packages available on these systems just doesn’t compare. I did a brief amount of research, according to the FreeBSD manual, there are “over 30,000” ports available. In comparison, there are over 90,000 packages available on the AUR, and all of those are in addition to the ~13,000 packages in the official Arch repositories. If I want to obtain a piece of software, even if it isn’t in the arch repos, odds are, someone has already gone through the trouble of figuring out how to build/package it, and has added the PKGBUILD to the AUR.
This way of doing things is so much more elegant compared to how things are done on Debian or Red Hat-derived distros, where the solution to the problem of a piece of software not being in the official repos is to either (1) scour the internet and try to find if the developer maintains a repo for your distro, (2) look to see if a third party has packaged the software for your distro, and hope and pray that they maintain it, or (3), compile the package yourself, after manually hunting down all the various libraries the application needs, determining what they’re packaged as for your particular distro. The third solution doesn’t handle updates at all, unless the application’s developer has built-in an update checker into it.
Things are getting better as snaps and flatpaks gain popularity, but both of those systems have lots of issues of their own, and arguably aren’t anywhere near as good as a proper native package for your distro. Flatpaks don’t really work for CLI tools. Snaps are stupidly slow. Both snaps and flatpaks still struggle with theming. Applications installed with either take up way more space than their natively-packaged equivalents.
Things are getting better as snaps and flatpaks gain popularity, but both of those systems have lots of issues of their own, and arguably aren’t anywhere near as good as a proper native package for your distro. Flatpaks don’t really work for CLI tools. Snaps are stupidly slow. Both snaps and flatpaks still struggle with theming. Applications installed with either take up way more space than their natively-packaged equivalents.
Flatpaks would beat native packages if they didn’t have a trillion papercuts and issues. I’m on NixOS because I want to avoid using flatpak.
quantity doesn’t always mean quality and when the subject is aur, i wouldn’t count that as a metric. there are lots of orphaned packages, packages that have their source / binary / git versions, older libraries etc.
it USED TO be a nice repository, i don’t why. but it’s one of the main reasons i’m keeping away from arch because i cannot trust those packages anymore.
Fair arguments. The AUR is huge compared to the operating systems that inspired it (no idea how packages/metrics are counted between different operating systems but it’s safe to say that more packages exist for Linux than in the FreeBSD realm), and it solves a problem that the Debian/Red Hat distributions are being faced with now that Flatpaks are essentially another packaging system ON TOP of whatever they have used for decades.
The setup is kind of a kind of a logical fallacy here. More people are using Debian and RPM based distributions than Arch Linux. That being said:
Arch Linux has the AUR because at the time it was developed, the standards for distributing software on Linux were either RPM or DEB repositories. AUR was a necessity because one could get software on those distributions from the official vendor, but nobody was supporting Arch Linux. So it was a stopgap, an equalizer for one outlier platform.
It’s hardly the first such repository: FreeBSD ports and NetBSD pkgsrc predate the AUR by over a decade. Slackpkg predates AUR by a couple of years as well, though possibly not slapt-get. Gentoo has portage. Anyway, they took an idea that was already well-established, and catered it to a distribution that had fewer software options than major distributions.
These days it’s still the same scenario: a placeholder, to equalize what’s available for Arch Linux users versus other distributions.
People use Arch because it is a rolling release with a well-documented wiki. AUR is a nice perk, but hardly the main reason that people are using Arch Linux, given that other similar systems have existed for older distributions and operating systems for longer.
I don’t believe the setup is a fallacy, the AUR is one of the main reasons I use Arch. Sure, other distros may have similar systems in place, but the number of packages available on these systems just doesn’t compare. I did a brief amount of research, according to the FreeBSD manual, there are “over 30,000” ports available. In comparison, there are over 90,000 packages available on the AUR, and all of those are in addition to the ~13,000 packages in the official Arch repositories. If I want to obtain a piece of software, even if it isn’t in the arch repos, odds are, someone has already gone through the trouble of figuring out how to build/package it, and has added the PKGBUILD to the AUR.
This way of doing things is so much more elegant compared to how things are done on Debian or Red Hat-derived distros, where the solution to the problem of a piece of software not being in the official repos is to either (1) scour the internet and try to find if the developer maintains a repo for your distro, (2) look to see if a third party has packaged the software for your distro, and hope and pray that they maintain it, or (3), compile the package yourself, after manually hunting down all the various libraries the application needs, determining what they’re packaged as for your particular distro. The third solution doesn’t handle updates at all, unless the application’s developer has built-in an update checker into it.
Things are getting better as snaps and flatpaks gain popularity, but both of those systems have lots of issues of their own, and arguably aren’t anywhere near as good as a proper native package for your distro. Flatpaks don’t really work for CLI tools. Snaps are stupidly slow. Both snaps and flatpaks still struggle with theming. Applications installed with either take up way more space than their natively-packaged equivalents.
Flatpaks would beat native packages if they didn’t have a trillion papercuts and issues. I’m on NixOS because I want to avoid using flatpak.
I’m wondering why flatpaks don’t work for command-line tools
quantity doesn’t always mean quality and when the subject is aur, i wouldn’t count that as a metric. there are lots of orphaned packages, packages that have their source / binary / git versions, older libraries etc.
it USED TO be a nice repository, i don’t why. but it’s one of the main reasons i’m keeping away from arch because i cannot trust those packages anymore.
Fair arguments. The AUR is huge compared to the operating systems that inspired it (no idea how packages/metrics are counted between different operating systems but it’s safe to say that more packages exist for Linux than in the FreeBSD realm), and it solves a problem that the Debian/Red Hat distributions are being faced with now that Flatpaks are essentially another packaging system ON TOP of whatever they have used for decades.
Yeah, the Arch Wiki is incredible, even as a non-Arch user, it’s such a valuable source of knowledge.