Note: This page is only a draft. Please ignore it until I finished writing it.
Build Host (http://stackoverflow.com/questions/5139403/whats-the-difference-of-configure-option-build-host-and-target) This page describes how you can use an already set up build environment to automate building and uploading ARM packages. This article assumes that you have already a build environment set up. However, if you have not you can find information about that on the Build Environment page.
We are assuming you're working as root in your build environment and that you are familiar with building and uploading packages manually. If you are not, you should read Repositoies as well.
autobuild? is a collection of shell scripts we assembled for automation of the build process. Install them in the build environment as we need them. Additionally you will need repo-man, rsync and Git.
pacman -S autobuild repo-man rsync git Configure the PKGBUILD and binary repository
You have to configure the Git repository as well as the binary repository to be accessible from the build environment. The Repositories? page explains how to archieve that. For the Git repository user access (retrieval only) will suffice, but you'll need developer access to the binary repository as you most likely want to upload your packages after you built them.
We will assume the Git repository is available in ~/abs and the binary repository in ~/pkg.
Setting up a cronjob
To automate building you have to join some commands from the autobuild package together. First you should make sure your repositores are updated.
cd ~/abs git pull
cd ~/pkg repo-man pull Using buildList -m you can get a list of packages which are updated in the Git repository but which have not yet been built for the binary repository.