[aur-dev] .SRCINFO: handling of commits lacking an update and in general

Gordian Edenhofer gordian.edenhofer at gmail.com
Sun Jul 26 16:34:28 UTC 2015

On Sun, 2015-07-26 at 14:48 +0200, Peter Mattern wrote:
> Hello.
> Considering the short time AUR 4 is in use the number of commits 
> lacking 
> an update of .SRCINFO seems to be rather high.
> The resulting problem is a cosmetic one only as the actual PKGBUILD 
> functionality isn't affected but only the package's web page not 
> updated 
> accordingly.
> Yet I wonder whether it would be helpful to reject commits lacking 
> the 
> update of .SRCINFO if feasible.
> Actually I wonder as well whether it wouldn't even be better to not 
> have 
> .SRCINFO written by the packagers before uploading a commit but by 
> aurweb when commits are received.
> This would ensure that problems like the one stated above can't 
> happen 
> and I for one couldn't figure a downside so far.
> Regards,
> Peter Mattern

I am against calculating the .SRCINFO on the server because of the
already stated security issues. However I agree that it is a growing
problem for AUR helpers. A reasonable approach would be to at least
remind the user through git each time a commit with no .SRCINFO was
pushed. Despite being unable to rewrite the history, it is at least
easy to just push the .SRCINFO afterwards.

Best regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.archlinux.org/pipermail/aur-dev/attachments/20150726/d0f65b62/attachment.asc>

More information about the aur-dev mailing list