Don't update DiskUsage to 3.7.1 (3071)
This commit is contained in:
parent
51d5e2f84f
commit
39f0805366
|
@ -67,16 +67,19 @@ Build:3.4.3,3043
|
|||
cp extra/system.jar libs/
|
||||
buildjni=yes
|
||||
|
||||
Build:3.7.1,3071
|
||||
disable=how is scan5 built?
|
||||
commit=9b73d3a94249f4366e06532f03cd6cf26e2eb2d9
|
||||
patch=ndk-out.patch
|
||||
rm=jni/scan,assets/scan*
|
||||
prebuild=mkdir libs && \
|
||||
cp extra/system.jar libs/
|
||||
scanignore=res/raw/mimes
|
||||
build=$$NDK$$/ndk-build
|
||||
|
||||
Maintainer Notes:
|
||||
The system.jar is from AOSP - see extra/system.jar.README and
|
||||
[https://github.com/ivanvolosyuk/diskusage/issues/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
|
||||
|
|
Loading…
Reference in a new issue