Hey there, I'd like to fetch some comments / opinions regarding maintaining AUR packages with the help of automated build systems. I do maintain several packages in the AUR containing the typical files as `PKGBUILD`, `.SRCINFO`, files referenced in the `source()` section and a special script `update-version.sh`. This script is not mentioned in the PKGBUILD and not used during the build process. It contains the required steps to figure out the latest version of the package and to patch the PKGBUILD. This script is a) used to document how the package is updated and b) is used by my CI system (atm Jenkins) to check for updates and update the package. (Extra steps to verify the package is still building fine before doing any update are common to all packages and are executed after this package-specific script.) For most of my packages there were no complaints about this and users seem to be happy to get the updates usually delivered within an hour after release. Though in one package (librespeed-cli) I got two comments asking me to remove that script. Now I found no explicit statement in the package / AUR submission guidelines against this. Therefore I'd like to ask other maintainers / TUs for your opinions: Are you strictly against adding a script which documents / is used for the update? Is it fine to keep it there? Shall it be removed though doing no harm? Cheers Knut -- Knut Ahlers Software & Infrastructure Developer Web & Blog: https://ahlers.me/ GPG-Key: 0xD215AD7D (https://knut.in/gpg)