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

Don't update DiskUsage to 3.4.3 (3043)

Browse source
This commit is contained in:
Ciaran Gultnieks 2014-05-10 18:08:24 +01:00
parent 532d59fa6f
commit 65257b79f9
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
metadata/com.google.android.diskusage.txt
View file

@ -58,9 +58,25 @@ Build:3.4.2,3042
cp extra/system.jar libs/ cp extra/system.jar libs/
buildjni=yes buildjni=yes
Build:3.4.3,3043
disable=Build system issue, see maintainer notes
commit=9a06fa318639
rm=jni/scan,assets/scan
patch=ndk-out.patch
prebuild=mkdir libs && \
cp extra/system.jar libs/
buildjni=yes
Maintainer Notes: Maintainer Notes:
The system.jar is from AOSP - see extra/system.jar.README and The system.jar is from AOSP - see extra/system.jar.README and
[https://code.google.com/p/diskusage/issues/detail?id=19] [https://code.google.com/p/diskusage/issues/detail?id=19]
The build system complains that native code should have been built but none
was packaged. This is partially correct - it's 'packaged' in the assets
directory, for some reason. This does highlight a problem, because it means
that the app will only work on ARM, but Android and the F-Droid client don't
know that. Really it should be packaged properly. But should we allow the
build to go through anyway?
. .
Auto Update Mode:None Auto Update Mode:None