Arch Linux – Best Tips for Beginners?
-
You definitely do not need to use any pacman wrappers to build a package from the AUR. Those tools make it easy, yes, but are not required.
Building a package can be as simple as
git clone AURpackageherecd AURpackageheremakepkg -si
-
"Arch" for people who think Arch is too easy.
-
lol Arch wasn't hard and neither was vanilla NixOS, in fact NixOS was easier
-
Arch was the distro that got me to stop distro-hopping. It's stable, it has a rolling release, and it's mine (as in, customizable, manageable).
I guess, if there's anything I wish I'd known off the bat is that the Arch documentation is probably the best available. So much so, a LOT of it applies to Linux in general and not strictly to Arch.
https://wiki.archlinux.org/title/Main_page
If something breaks, READ the error messages, understand each component, and check the wiki, there's a very high chance the troubleshooting section has the exact issue laid out.
-
Yes, and I love it
Maybe I should have added “if going the arch route”..
-
Not if you have a weird app that only installs with a self-executing tarball. But for initial setup, sure.
-
Um. Ya, I guess. Ok.
First, how do you keep that package up to date?
Real question though is, do you really think that is better than “yay -S AURpackagehere” or even “paru AURpackagehere”?
-
To update the package, you use git to pull the latest branch code and repeat the process. You should double check if there are dependency changes though.
Like I said, its easier with a pacman wrapper, but not necessary.
-
Sure unless you want to use AUR and now what do they recommend?
-
They have a whole wiki for the AUR.
-
Yes. Thank you. My question (or point) was how you know that the package needs to be updated? As you point out, I need to do that for dependencies as well.
You are certainly correct though. You can pull AUR packages and build them without yay or paru.
-
Per the Arch Wiki, the burden of figuring out if there are updates to your AUR package falls on you.