Find a file
Ciaran Gultnieks f4ec31efa5 Revert "SparkleShare: Add patch to allow install on camera-less devices."
This reverts commit 998d42fd4e84afa09a2803dc25d61437d042a6d5. There
doesn't seem to be any point in patching this:
a) It's already been in the repo a long time
b) If we issue another version of a package, with the exact same
version name and code, how is anybody supposed to know which is which?
(I realise in this case it wouldn't make much difference, but the
general principle is important)
c) There is a technical problem in that if a different version of what
should be the same apk is pushed to the repo, installations will be
rejected by the client (until an update is done) because they will see
that the file they download is not what it was supposed to be.
d) The developer says he is fixing it in the next release anyway.
2012-02-22 15:28:59 +00:00
build Metadata: enabled OpenDocument reader 2012-02-11 15:26:38 +00:00
metadata Revert "SparkleShare: Add patch to allow install on camera-less devices." 2012-02-22 15:28:59 +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

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.