On Tue, Jun 15, 2021 at 02:23:56PM +0300, Caleb Maclennan via aur-general wrote:
On 2021-06-15 04:19, George Rawlinson via aur-general wrote:
What's your package maintenance/procedure like? I'm always interested in seeing how people approach this so I can steal ^W borrow ideas.
I use `aurpublish` to manage AUR repos, plus a couple hand rolled scripts. One signs and publishes packages I built to my own package repository, the other steps me through the update/build process. The process starts by opening my editor (nvim of course) where I bump the version and clean up anything else that catches my eye. Then it updates checksums and attempts to build the package (both on the host system and in a chroot). If that works it installs it (I only build from systems where I actually *use* packages, so this works. Once installed I do a quick check to make sure nothing broke. For apps this usually means just running them and making sure they don't segfault or complain about deps. For system services I restart the service and make sure it still functions. If that's good then the result gets committed (aurpublish taking care of updating the .SRCINFO) and I push to the AUR repo plus my aurpublish repo and run the other script to publish the package and re-sign my repo.
How do you stay on top of package updates? Do you have any hand rolled scripts to check for updates or do you use existing tooling?
P.S. Was it you that approved the mass deletion of anything Google Play Music related from the AUR recently without checking which projects actually had been updated to work with YouTube Music even if they still have GPM in their name or description?
Ooooohh, backfire 😃!