kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-10-03 17:50:11 +02:00
Code Activity

Make config location clearer in manual?

Browse Source
This commit is contained in:
Ciaran Gultnieks 2012-08-08 10:30:39 +01:00
parent 6eb2229a3b
commit 2b46fa1c99
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/fdroid.texi
View File

@ -151,8 +151,9 @@ git clone git://gitorious.org/f-droid/fdroiddata.git
Regardless of the intended usage of the tools, you will always need to set
up some basic configuration details. This is done by creating a file called
@code{config.py} which you should do by copying from @code{config.sample.py}
and then editing according to the instructions within.
@code{config.py} in the data directory. You should do this by copying the
example file (@code{config.sample.py}) from the fdroidserver project to your
data directory and then editing according to the instructions within.
Once configured in this way, all the functionality of the tools is accessed
by running the @code{fdroid} command. Run it on its own to get a list of the
@ -651,7 +652,9 @@ good idea if it's heavily customised.
@item rm=<relpath>
Specifies the relative path of file to delete before the build is
done. The path is relative to the base of the build directory - i.e.
the directory that contains AndroidManifest.xml.
the root of the directory structure checked out from the source
respository - not necessarily the directory that contains
AndroidManifest.xml.
@item antcommand=xxx
Specify an alternate ant command (target) instead of the default