So quick question. Im maintaining an AUR package that grabs sources from git. How should I update the package? Will the package be automatically updated when the git repo has new commits, or do I have to manually increment the pkgrel variable in the PKGBUILD or is there something else I should be doing?
Last edited by Zygote (2014-04-03 07:04:44)
I think that's something I forgot to mention in your other thread -- write a pkgver function to update the PKGBUILD's pkgver. The wiki link I posted in that thread (about VCS PKGBUILD standards) has the details.
Regardless, when you run makepkg against a (correctly written) PKGBUILD, it pulls in the upstram changes and builds against them.
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD
Making lemonade from lemons since 2015.
Im maintaining an AUR package that grabs sources from git. How should I update the package?
As a maintainer, you shouldn't "update" anything. As long as the PKGBUILD file successfully builds the package then it's good!
Will the package be automatically updated when the git repo has new commits
No, it will not. There is nothing automatic about the AUR.
do I have to manually increment the pkgrel variable in the PKGBUILD or is there something else I should be doing?
Updating a package that relies on git is the responsibility of the end user.
As an end user, it's my responsibility to read the project's commit messages and mailing lists and bug reports, decide that the software is stable, and when I have enough time, run "makepkg" (or an AUR helper) to create a fresh new package based on the latest source code from the git repository.
The only thing to add to the above is that the AUR package name should have -git appended to the name. This makes it clear to users what they are getting and that it is up to them to make the choices mentioned above. Apparently some AUR helpers even use these -git -dev type package names to rebuild everything for you with the right flags.
Thanks for all the input! Ive added a pkgver function and hopefully things are working well.
Quick question. When is the pkgver run exactly? Currently, the package on AUR shows r40.6657d43. However, the source on github is currently at r42. Should I update the package on the AUR every now and then to reflect this or should I just leave it?
Just leave it: it will be updated whenever someone downloads it and runs makepkg.
Ah really? Thats awesome! Thanks!