AUR web interface

Tasklist

FS#3025 - Improve source and md5sum checks

Attached to Project: AUR web interface
Opened by dtw (dibblethewrecker) - Monday, 01 August 2005, 15:08 GMT
Last edited by Callan Barrett (wizzomafizzo) - Thursday, 27 March 2008, 09:11 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 1.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

At the moment as long as the source and md5sums are included in the PKGBUILD the AUR will not reject the pkg - REGARDLESS of whether they are filled or not :)

I have a suggestion that also account for CVS/SVN build which often have no source array requirements. At the moment the source field must be included.

Check for a source field
- If source= found but empty maybe fail (CVS/SVN PKGBUILDs should not include a source field)
- If source= found and filled then check for m5sums=
- should also be able to match the number of source entries to the number of md5sum entries easily to check they are complete
- If source= not found at all then skip md5sums= check completely as we assume no source at all i.e CVS/SVN build
This task depends upon

Closed by  Callan Barrett (wizzomafizzo)
Thursday, 27 March 2008, 09:11 GMT
Reason for closing:  Won't implement
Additional comments about closing:  All these checks would reject valid PKGBUILDs.

Loading...