[aur-general] The Impossible, or: Static analysis of PKGBUILDS (was Re: Enforcing AUR package quality)

[Robin Broda]

TL;DR:

I think this is a people-problem that cannot be solved like this.

alad pointed out on IRC that:
> the bug reports pre-srcinfo which tried to parse bash and terribly failed
> people actually hacked around their PKGBUILDs so the right information would show on aurweb

This is going to repeat itself.

If you're looking to increase the mean quality of AUR PKGBUILDs,
the first thing that might have to be done is a change of policy.

I think that if "builds in a clean chroot" (+ a better page on how to)
was a rule for AUR submission, people would *automatically* take more care.

-- 
Rob (coderobe)

O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20190301/127f2dd9/attachment.sig>