I talked a bit with neotuli about integrating a package scraper into the aur. Here is how I envision it working in an integrated fashion.
The aur would include either an xml-rpc page, or a soap page. I would lean more towards soap with a wsdl definition, so that clients are even simpler. Dead simple.
Here is an example client written in ruby, that would be functional for searching for app names:
#!env ruby require 'soap/wsdlDriver' searchstring=ARGV.join(" ") WSDL_URL="http://aur.archlinux.org/soapy.php?wsdl" soap=SOAP::WSDLDriverFactory.new(WSDL_URL).createDriver result=soap.search(searchstring) puts result
It would be used like this:
./scraper toon unsupported-kde gartoon 1.3-1 Gartoon is a fun looking icon pack for KDE Maintainer: Pointer Url: http://aur.archlinux.org/packages.php?do_Details=1&ID=1199
Or something similar.
If anyone is interested, I have a soap web service setup on a little web app. If you want to see some code, or test it out, shoot me a pm.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
brilliant idea cactus... AUR style emulation of "pacman -Ss"
The only thing I fear is that it will export the "id" which some people don't like (getting the PKGBUILD and automating it after that point is trivial)
In order to solve that, I'd simply put a "Unsafe: Yes" flag in the output, to determine if it's been verified...
which goes to the next step - allowing a TU to verify a PKGBUILD as safe for consumption.
Hmmm... I'm rambling, but to me it sounds good. Here's the steps:
Add package "Safe = yes|no" flag. On upload/upgrade, package is always set to unsafe... TUs allow to toggle flag.
With packages exposed through soap, combine with Dusty's aurbuild script, and viola... we now have a "aurpac" which will only allow a user to auto-build validated PKGBUILDs
Yes indeed, we did talk about this.
The first version of this system would certainly only be a pacman -Ss equivalent, no PKGBUILDs transfered.
I'm not sure yet, but we're thinking about going ahead and letting people use cvsup on unsupported... but then we'd also have to add code so that those directories actually get deleted when the package does....
Right, well anyhow...a big warning in RED would probably be good if we ever allow direct download of PKGBUILDs through the same interface as this.
I should also say that this interface would only be for unsupported, [community] is already taken care of because it works no differently than an official repo.
The suggestion box only accepts patches.