missytake/fdroiddata
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

OsmAnd~: Prepare for 2.0.1 (201)

Browse source
This commit is contained in:
Boris Kraut 2015-04-29 22:59:44 +02:00
parent 714dcb5a56
commit dcce26dec9
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
metadata/net.osmand.plus.txt
View file

@ -139,9 +139,9 @@ Build:1.9.5,197
ndk=r10d ndk=r10d
#use v2.0.0 branch #use v2.0.0 branch
Build:2.0.0,201 Build:2.0.1,201
disable=testing disable=wait for newer builds
commit=bdd5a30f79e73d3968431f2831bbd624161cde8e commit=dedb3ac8c4896c3cff9889869da58132eb91c601
subdir=android/OsmAnd subdir=android/OsmAnd
submodules=yes submodules=yes
build=../../build build=../../build
@ -155,12 +155,12 @@ No UCMs apply because git never contains actual releases, only pre-releses.
The build instructions have been moved to a script in the root of the repo, The build instructions have been moved to a script in the root of the repo,
'build'. This way it can be updated along with the submodules. 'build'. This way it can be updated along with the submodules.
Upstream now uses gradle. We invoke gradle from within ../../build which might = 2.0.0+ =
break on the BS. We should try to use gradle=fullLegacyFat to build like `gradle Upstream now uses gradle. We do some preparations in ../../build but try to
clean assembleFullLegacyFatRelease`. Versioname is off, e.g. "2.0.02.0" instead keep the main build within the recipe via `gradle=`.
of "2.0" -- it looks like our forcing is no longer necessary.
I don't know where the 2.0.1 is comming from.. 2.0.1 commits used for release build don't compile; same for head. Waiting
for newer builds.
. .
Auto Update Mode:None Auto Update Mode:None