I have edited my question for clarity.
yay update a package I initially installed from my own local PKGBUILD when I update my PKGBUILD file? In other words, can AUR helpers be used for packages that are not in AUR?
Details: Say I create a PKGBUILD file locally and use it to install a package that is not in the AUR, using these steps:
- Acquire the build files, including the PKGBUILD and possibly other required files, like systemd units and patches (often not the actual code).
- Verify that the PKGBUILD and accompanying files are not malicious or untrustworthy.
- Run makepkg -si in the directory where the files are saved. This will download the code, resolve the dependencies with pacman, compile it, package it, and install the package.
After I have followed the steps above to install a package without using an AUR helper, can I later keep the package updated with an AUR helper? Of course, since the package is not in the AUR, I will have to update my local PKGBUILD file when the developer releases a new version. Assuming I do this, will a good AUR helper (e.g.,
yay) be able to correctly run
My motivation is to maintain the same workflow for these non-AUR packages, which means I wish to use an AUR helper to keep them updated.
My question is, more broadly, how do the AUR helpers determine when a package needs to be updated? Do they rely exclusively on the online repo or can they make that determination for a local package that is not in the AUR?
If the answer to that last question is yes, what steps do I need to follow when using my own local PKGBUILD? It is clear that I need to update my PKGBUILD file when a new version of the application is released. Do I need to put the PKGBUILD files in a certain location for a tool like
yay to find them? Do I need to "register" the local PKGBUILD file with
yay in some way? Do I need to follow a certain convention in regard to version numbers?