Ok, I can do one better now.
I've built a raspi with raspian and set it up as a development environment. Then pulled the latest trunk from aprx svn and built that as a debian package.
The result is here:
This is a debian Raspbian package, built off an up-to-date build of Debian for Raspberry Pi.
I understand your original request was for a complete IMAGE of a ready-to-go RasPi image with APRX in place, but 1) I don't know how to do that, and 2) I don't want to undertake keeping a complete image up-to-date. This way, all I have to do is run apt-get upgrade and re-run svn up && dpkg-buildpackage once a week to keep the package completely current with Raspbian. If I build a "Win32Imager" version, I'd put it up and 6 months from now I'd forget about it until I got some angry emails complaining that it was out of date or broken in some way. The whole debian distribution system is built around the concept of a base set of packages, and then add-ons to that base set that can be provided by anyone.
Please post any questions to the list.
John Gorkos
AB0OO