FS#7479 - Ability to Enter PKGBUILDs

Attached to Project: AUR web interface
Opened by Dusty Phillips (Dusty) - Wednesday, 20 June 2007, 18:24 GMT
Last edited by Callan Barrett (wizzomafizzo) - Sunday, 08 June 2008, 18:23 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 1.2.9
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Not sure if this has been suggested, but it would be nice to allow PKGBUILDs to be entered or edited directly from the web interface. For the majority of packages, the only file included in the tarball is a PKGBUILD, and for the majority of updates, this is the only file updated. It would be easier for some users to copy-paste their PKGBUILD into the web interface than to create a tarball and upload it.
This task depends upon

Closed by  Callan Barrett (wizzomafizzo)
Sunday, 08 June 2008, 18:23 GMT
Reason for closing:  Won't implement
Additional comments about closing:  If you think about this for a while it doesn't make a whole lot of sense to implement in my opinion, testing has the ability to submit raw PKGBUILDs now so this is probably enough.
Comment by tardo (tardo) - Tuesday, 23 October 2007, 06:37 GMT
I started to write a patch for this then realized the work involved:

1. Get current PKGBUILD into <textarea />
2. On submit, parse new PKGBUILD using pkgbuild parser
3. Check for errors in new PKGBUILD
4. Repackage
5. Update DB.

I think it would be much easier to just submit a new PKGBUILD (which can be done RAW) than rewrite most of the current code.

All pending on AUR 1.5 of course.

Loading...