aurch VS yay

My personal AUR helper builds AUR packages in an nspawn container. Thinking about scripting the automation of running them in dedicated nspawn container as well.

I ended up writing my own AUR helper that sets up aurutils inside an nspawn container. It does prompt for inspecting and/or modifying git cloned files before building. However, it omits other typical AUR helper features like building/updating multiple packages at once. On the other hand, it transparently manages required gpg keys and AUR dependencies. https://github.com/Cody-Learner/aurch

I did it using a systemd nspawn container. I made my AUR helper as both an interesting scripting project and a proof of concept for myself. https://github.com/Cody-Learner/aurch

Reinventing the wheel has been an great way for me to learn more about shell scripting and Arch packaging in general. ie: https://github.com/Cody-Learner/aurch

I use pacman to work on non default locations in my AUR helper. https://github.com/Cody-Learner/aurch

I've been using my own AUR helper over the last year without issue. https://github.com/Cody-Learner/aurch

Details: https://github.com/Cody-Learner/aurch/blob/main/aurch

yay is a robust and user-friendly AUR (Arch User Repository) helper for Arch Linux and Arch-based distributions written in Go.

paru has better defaults and --chroot, whereas it's still an open issue for yay.

If you use AUR packages, you might want to use an AUR helper that wraps pacman, like paru or yay.

This one: https://github.com/Jguer/yay Didn't know there were others..

you can use an aur helper like yay

Yay is hopelessly broken, it pretends to rebuild stuff when, in fact, it doesn't. See: https://github.com/Jguer/yay/issues/2153