On Tue 28 Jul 2015 11:27 -0500, Doug Newgard wrote:
On Tue, 28 Jul 2015 16:52:35 +0200 Peter Mattern <pmattern@arcor.de> wrote:
What exactly is the benefit of an isolated upload of a PKGBUILD that doesn't change the package itself at all, in particular now that Git is used and everybody has got a local checkout at hand anyway? If there should be any benefit at all it for sure doesn't outweigh disadvantages like outdated package sites or RPC issues affecting AUR helpers.
And as soon as a modification of PKGBUILD does change the package at least a release bump is justified and thus an update of .SRCINFO as well.
All commits are checked, not just HEAD when you push. Adding this check would make it so you cannot have commits like this at all, even if you only push later when there is another change.
And how about something as simple as changing the maintainer tag?
Scenario: You add an install script in the PKGBUILD and you forget to add it to the commit. You add a followup commit to add the script. There are no changes to PKGBUILD.