MuPDF: Provide details on versioning conflict

metadata/com.artifex.mupdfdemo.txt

@@ -61,18 +61,7 @@ Build:1.2-MIPS,52
         make generate
     buildjni=yes
 
-Build:1.4,53
+Build:1.5-ARM,53
-    disable=Doesn't build, just hangs
-    commit=1.4
-    subdir=platform/android
-    submodules=yes
-    forceversion=yes
-    prebuild=sed -i 's/armeabi-v7a/armeabi armeabi-v7a/g' jni/Application.mk && \
-        cd ../.. && \
-        make generate
-    buildjni=yes
-
-Build:1.5,60
     disable=wip
     commit=1.5-ios-appstore
     forcevercode=yes
@@ -88,6 +77,22 @@ Build:1.5,60
 Maintainer Notes:
 Source code is not up to date as far as android versioning goes. Our version
 codes probably differ from the official ones.
+
+Looking at http://mupdf.com/downloads/ and platform/android/jni/Application.mk
+the version scheme is like:
+
+armeabi = baseversion + 0, e.g. mupdf-1.5-android-50-armeabi.apk
+armv7 = baseversion + 1, e.g. mupdf-1.5-android-51-armv7a.apk
+x86 = baseversion + 2, e.g. mupdf-1.5-android-52-x86.apk
+mips= baseversion + 3, e.g. mupdf-1.5-android-53-mips.apk
+
+I'd assume baseversion corresponds to the versionName, e.g. 1.5 = 50. This
+would make 1.6 starting with verCode 60 up to 63 for the mips release. However,
+the verCode has been 50 for ages (~2013!) and the devs in #ghostscript said:
+"The android apk version numbers bear no resemblance to the app version."
+
+Documents:
+http://www.mupdf.com/docs/how-to-build-mupdf-for-android
 .
 
 Auto Update Mode:None