# Climbing the PKGBUILD learning curve 🤔

**URL:** <https://forum.endeavouros.com/t/climbing-the-pkgbuild-learning-curve/80143>\
**Category:** Pacman & AUR helpers\
**Created:** [June 13, 2026, 4:19pm UTC](https://forum.endeavouros.com/t/climbing-the-pkgbuild-learning-curve/80143 "2026-06-13T16:19:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [June 13, 2026, 4:21pm UTC](https://forum.endeavouros.com/t/climbing-the-pkgbuild-learning-curve/80143/2 "2026-06-13T16:21:28Z")

</div>

This is a good start:

> [@AUR PKGBUILDs](https://forum.endeavouros.com/t/aur-pkgbuilds/6669/18):
>
> The AUR is one of the safest ways to install software, just because it is so transparent. But it does not tolerate just looking up the package in Pamac and clicking on the Build button, or doing yay package\_name blindly. It requires that the user knows what’s going on. That’s why I recommend trying to build at least one package manually, to understand what’s going on, before using an AUR helper like pamac or yay. yay has a nice feature that allows you to inspect a PKGBUILD file before installin…

Also, it is worth noting while there are complicated PKGBUILDs out there, most of them are very simple.

The number one thing you should be doing is checking everything in the `source` array.

Also, if any of the dependencies are other AUR packages, you need to check those too.

---

_[View the full topic](https://forum.endeavouros.com/t/climbing-the-pkgbuild-learning-curve/80143)._