From 551c08cc61d69db57d5f2bb83baaae8e4fcfdc0d Mon Sep 17 00:00:00 2001 From: Ciaran Gultnieks Date: Fri, 22 Nov 2013 19:38:19 +0000 Subject: [PATCH] Update AnagramSolver (com.as.anagramsolver) to 2.05 (12) --- metadata/com.as.anagramsolver.txt | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/metadata/com.as.anagramsolver.txt b/metadata/com.as.anagramsolver.txt index 2e48785340..1bba1e4a36 100644 --- a/metadata/com.as.anagramsolver.txt +++ b/metadata/com.as.anagramsolver.txt @@ -33,8 +33,19 @@ Build:2.0,11 git submodule init && \ git submodule update +Build:2.05,12 + commit=c3c48c2e + init=sed -i 's%git@github.com:%https://github.com/%' .gitmodules && \ + sed -i 's%git@github.com:%https://github.com/%' .git/config && \ + echo 'android.library.reference.1=external/actionbarsherlock/actionbarsherlock' >> project.properties && \ + echo 'android.library.reference.2=external/changelog/library' >>project.properties && \ + echo 'android.library.reference.3=external/storageutils' >>project.properties && \ + git submodule init && \ + git submodule update + Maintainer Notes: -No tags, and no clear marking of release points in commit comments. +No tags, and historically no clear marking of release points in commit comments. +Look out for binary apk changing in source repo though. Uses git submodules for dependencies after 2.0, but the project.properties indicates that the developer is not actually using them, so beware of