[aur-dev] AUR Android app

Pedro Veloso pedro.n.veloso at gmail.com
Sun Apr 21 16:13:35 EDT 2013

Thank you for the tips @Chris. That was somewhat what I was thinking as
well ;)

I've started to code the application today, and even made a forum post to
ask for icons and other graphic content from community, which might be
interested in providing such things. ->

The project is on GitHub : https://github.com/pedronveloso/AURHelperDroid
And it is published under the Apache 2.0 license.

For those who want to test but don't want to compile the
app themselves here you've the APK:

And for those that don't have an Android you can check the pics I posted on
the forum post ;).

This is a very early build, right now I haven't actually made any of the
logic for the RPC. I've though about the application in the past few days
before starting to implement it and right now I got the main flow, features
and requirements on paper. Among those features I though it makes sense for
the app to have a place to see the latest packages, I done it via the AUR
RSS feed. That item is already implemented in this first build, although it
still needs to send feedback to the user that something is loading when he
enters the "New" screen and a ton of other things like caching, etc. As I
said it is very premature still, but I just wanted to share the progress
like I said I would.


On Sat, Apr 20, 2013 at 9:12 AM, Chris “Kwpolska” Warrick <
kwpolska at gmail.com> wrote:

> On Sat, Apr 20, 2013 at 2:27 AM, Pedro Veloso <pedro.n.veloso at gmail.com>
> wrote:
> > The notifier for package maintainers should be easy to implement, I'm
> > assuming it is basically keeping track of the "OutOfDate" field.
> The AUR mail notifications send info about new comments, marking as
> outdated, deletes (TU), merges (TU) and orphans (TU/user).  Doing the
> first one requires ugly web scraping.  The others are easy to
> implement with a msearch call, described below.
> Just throw a HTTP request to
> https://aur.archlinux.org/rpc.php?type=msearch&arg=USERNAME, decode
> the JSON, put the results in a database (or a csv file) storing only
> the names and out-of-date status.  Then, inform the human about
> existing out-of-date packages.
> On each subsequent call to the RPC, compare the database results with
> data you just downloaded from there.  Package wasn’t out of date and
> now it is?  Tell the human.  Package isn’t there anymore?  Tell the
> human that it was deleted, merged or orphaned.  And then save the
> newly downloaded data, overwriting previous database results.
> --
> Kwpolska <http://kwpolska.tk> | GPG KEY: 5EAAEA16
> stop html mail                | always bottom-post
> http://asciiribbon.org        | http://caliburn.nl/topposting.html

More information about the aur-dev mailing list