fdroiddata

Go to file

Paul Sokolovsky 103d39c2e9 Patch before running prebuild commands. Sometimes an application provides a script to initialize its build environment, and it may be required to patch such a script before running it (typical case is hardcoding developer's local paths). More generally, "declaritive" ways of changing code (e.g., forceversion, patch, etc.) should be preferred to prebuild, which should be used as the last resort (as it is too generic and thus verbose). So, it's right ordering in that respect either.		2012-02-24 03:21:00 +02:00
build	Metadata: enabled OpenDocument reader	2012-02-11 15:26:38 +00:00
metadata	Metadata: updated droidnotify version	2012-02-23 09:47:05 +00:00
stats	Metadata: various version updates	2012-02-21 21:46:01 +00:00
.gitignore	Forgot to gitignore unsigned directory	2012-02-04 09:48:25 +00:00
COPYING	Initial files	2010-10-21 23:26:38 +01:00
fdroid-icon.png	Icon for repository	2010-12-17 11:00:18 +00:00
README.buildserver	Latest buildserver wip	2012-02-21 00:01:07 +00:00

README.buildserver

Integrating the build server setup into the main scripts is a work in progress. Some things may
not work properly yet. Talk to CiaranG if you're trying to use this and have problems.

Setting up a build server:

1. Install VirtualBox, vagrant and vagrant-snap
2. Create (or get - ask CiaranG, or wait until I replace this with a download link!) a standard
   Debian Squeeze vagrant-compatible base box called 'debian6-32'
3. Run makebuildserver.sh. This will take a long time. The end result is a new base box called
   'buildserver'.

You should now be able to use the --server option on build.py and builds will
take place in the clean, secure, isolated environment of a fresh virtual
machine for each app built.