-# Installing Exim Build Farm Client
-So you want to give back to the Exim project but don't know how? Being a member of the Exim Build Farm is one way you can help. If your distro and version is not on the list that is currently being built, or if your build configuration is drastically different than others with your distro and version, then submit a request to join the farm. This Installation page is starting from the assumption that you have already submitted your request and the farm administration has sent you an email with your machine alias and secret password.
+# Installing Exim BuildFarm Client
+So you want to give back to the Exim project but don't know how? Being a member of the Exim BuildFarm is one way you can help. If your distro and version is not on the list that is currently being built, or if your build configuration is drastically different than others with your distro and version, then please consider submitting a request to join the farm. I would also like to point out that the Debian project has excellent Exim coverage on Experimental their [Build Farm](https://buildd.debian.org/status/package.php?p=exim4&suite=experimental). We're not discouraging you from joining the Exim BuildFarm if you're Debian or Debian derivative, but merely want to acknowledge the excellent job the Debian project already does with it.
+
+This Installation page works on the assumption that you have already submitted your [Exim BuildFarm Application](http://eximbuild.mrball.net/cgi-bin/register-form.pl) and the BuildFarm administration has sent you an email with your machine alias (aka _animal_) and secret password, which you will enter in step 9 below. If you just want to run the build farm client and never submit the results, you call simply run everything with the --test option and it will still work. If you ever run it without --test, it will still work, but the server will reject the feedback because it's from an unknown _animal_.
## Install Steps
1. Make sure that all required packages for Exim to build successfully are installed. The minimal package requirements are the basic suite of compiler tools and basic libraries. You will also need to install the ccache package.
17. The official process can be kicked off by running `/home/farm/code/run_cron.sh --run-all`. This will run the default build configuration, keep track of the git repository status, and upload the build results to the server.
18. Once that command runs with no complaints, add it to the **farm** user crontab. You can run it at whatever frequency you choose, I suggest 1 hour. If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other.
-## Overview
-
-In the default configuration, a full rebuild of Exim will occur every 7 days, and it will also build and run the test suite. You can choose to also have it also build the docs, but there are several extra package requirements for it to build the documentation.
-
-Review your enabled features in the Makefile and make adjustments to your *build-farm.conf* to enable those features, using either the makefile_set, makefile_add, or makefile_regex. You may also receive requests from the developers to enable specific features on your build.
-
-The default build configuration will build all branches specified in a text file on the server. Most of the time this will only be HEAD, but occasionally the developers may have an interest in building some experimental code on a different branch. The above configuration will do all of it automatically for you. The *run_cron.sh* will also check the master repo at github and update itself (the Exim Build Farm Client software).
\ No newline at end of file
+## Further documentation
+* Details of options in [build-farm.conf](https://github.com/mrballcb/exim-build-farm-client/wiki/BuildConfigConf)
+* Details of [potential testing commandlines](https://github.com/mrballcb/exim-build-farm-client/wiki/TestingBuilds)
git://git.exim.org / buildfarm-client-wiki.git / blobdiff