kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-09 17:00:12 +01:00
Code Activity

There is no longer any Vagrantfile

Browse Source
This commit is contained in:
Daniel Martí 2013-12-30 17:02:19 +01:00
parent 6773d5e70b
commit 4ac7b02f53
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/fdroid.texi
View File

@ -1396,14 +1396,12 @@ boot, you need to set @code{GRUB_RECORDFAIL_TIMEOUT} to a value other than
-1 in @code{/etc/grub/default} and then run @code{update-grub}. -1 in @code{/etc/grub/default} and then run @code{update-grub}.
@end enumerate @end enumerate
You may also want to edit @code{buildserver/Vagrantfile} - in particular
there is a path for retrieving the base box if it doesn't exist, and an
apt proxy definition, both of which may need customising for your
environment.
With this base box available, you should then create @code{makebs.config.py}, With this base box available, you should then create @code{makebs.config.py},
using @code{makebs.config.sample.py} as a reference - look at the settings and using @code{makebs.config.sample.py} as a reference - look at the settings and
documentation there to decide if any need changing to suit your environment. documentation there to decide if any need changing to suit your environment.
There is a path for retrieving the base box if it doesn't exist, and an apt
proxy definition, both of which may need customising for your environment.
You can then go to the @code{fdroidserver} directory and run this: You can then go to the @code{fdroidserver} directory and run this:
@example @example
@ -1425,9 +1423,9 @@ can supply a pre-populated cache directory which includes not only these
downloads, but also .tar.gz files for all the relevant additions. If the downloads, but also .tar.gz files for all the relevant additions. If the
provisioning scripts detect these, they will be used in preference to provisioning scripts detect these, they will be used in preference to
running the android tools. For example, if you have running the android tools. For example, if you have
@code{buildserver/addons/cache/platforms/android-15.tar.gz} that will be @code{buildserver/addons/cache/platforms/android-19.tar.gz} that will be
used when installing the android-15 platform, instead of re-downloading it used when installing the android-19 platform, instead of re-downloading it
using @code{android update sdk --no-ui -t android-15}. using @code{android update sdk --no-ui -t android-19}.
Once it's complete you'll have a new base box called 'buildserver' which is Once it's complete you'll have a new base box called 'buildserver' which is
what's used for the actual builds. You can then build packages as normal, what's used for the actual builds. You can then build packages as normal,