Yay, PKGBUILD, makepkg - basic question

Some basic confusion on my part … perhaps this will be easy for someone to clear up?

I use yay routinely for installing new apps, updating, etc. As a result, I haven’t spent much time exploring the hands-on makepkg installation method (except when forced to do so by some driver or the rare one-off hardware patch).

QUESTION: If I were to manually makepkg and install apps myself more routinely, will I be bypassing the benefit of having yay subsequently take care of future app updates - as it so nicely does now?

Alternatively, would yay be aware of and update those apps I’ve installed without using yay (or pacman) myself … i.e., if such entries are also being added to the pacman/yay inventory anyhow?

As long as a package with the same name is in AUR, yay will update it.

1 Like

Simply put, yay will be aware of those packages. If those packages exist in the repositories, they’ll be updated as per usual, when updated, but as per the repositories PKGBUILD, not your local version.

1 Like

Also of note, if using yay --devel, this seemingly only updates -git packages installed via yay, not those installed via makepkg (regardless of whether they’re in the AUR).

Actually I’m getting inconsistent results with this. I haven’t quite worked out when it will, or won’t update a development package.

1 Like

@dalto @Bink Many thanks for the fulsome and prompt replies.
Onward I go!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.