|
|
|
|
|
|
by gbrown
1693 days ago
|
|
|
> I think you're confusing Arch with Gentoo or something - the Arch package manager is not from-source, it ships binaries just like apt. Perhaps you're thinking of the AUR Sorry, what I meant was: when I need to manage the version of something carefully, I just compile it from source and that's OK with me. My understanding is that people use the AUR for this on Arch, and the pains don't seem worth it. > The main thing that people like about it is the rolling release model Fair enough, though I've been pretty happy with the pace of update from, for example, Fedora. > That's very much a "cover-your-ass" type disclaimer, like a ToS that says you have no right to expect anything to work. Fair enough |
|
|
Nobody's making you use the AUR! If you want to 'make && sudo make install' you can do that all day long.
The AUR value add is that other people have already figured out recipes for how to take the equivalent of 'make && sudo make install' and generate a package you can mange with the package manager.
There exist plenty of tools to automate all AUR interactions, but none of these will ever be included in Arch's main repos, since they are not a core part of Arch itself. This is to maintain a sharp delineation between properly supported Arch packages and the more wild west AUR recipes. That said, once you download a PKGBUILD from the AUR, you can use the same official tools to build and install the package that are used for the distro proper.
When I want to build from source, and something isn't in the AUR, I just spend the 5 minutes to make a proper PKGBUILD for myself. It is very easy and it simplifies management of things.