From 6a4c53e5e9d6f1537851a23a168132d29d8183cf Mon Sep 17 00:00:00 2001 From: David Black Date: Sun, 14 Jul 2013 23:15:45 +0100 Subject: [PATCH] manual: more uses for forceversion --- docs/fdroid.texi | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/fdroid.texi b/docs/fdroid.texi index 746985ca..551ba4f3 100644 --- a/docs/fdroid.texi +++ b/docs/fdroid.texi @@ -637,7 +637,8 @@ It can be helpful to note information pertaining to updating from an earlier version; whether the app contains any prebuilts built by the upstream developers or whether non-free elements were removed; whether the app is in rapid development or whether the latest version lags behind the -current version; or whether the app supports multiple architectures. +current version; whether the app supports multiple architectures or whether +there is a maximum SDK specified (such info not being recorded in the index). @node Repo Type @section Repo Type @@ -780,7 +781,9 @@ If specified, the package version in AndroidManifest.xml is replaced with the version name for the build as specified in the metadata. This is useful for cases when upstream repo failed to update it for -specific tag, or to build an arbitrary revision. +specific tag; to build an arbitrary revision; to make it apparent that +the version differs significantly from upstream; or to make it apparent +which architecture or platform the apk is designed to run on. @item forcevercode=yes If specified, the package version code in the AndroidManifest.xml is