Bug#854483: [Android-tools-devel] Bug#854483: android-sdk: set default ANDROID_HOME

Yeah, ideally it would automatically find the SDK. But using ANDROID_HOME is how upstream works, and I doubt it'll be easy to change that behavior. I do want to find a good solution to this, but I think we need to first get it Debian Android Tools packages working using the normal Android

Bug#854483: [Android-tools-devel] Bug#854483: android-sdk: set default ANDROID_HOME

* Hans-Christoph Steiner [2017-02-08 09:33]: > ANDROID_HOME is not required for things to function as far as I know. Without it I get: SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable. when compiling a

Bug#854483: [Android-tools-devel] Bug#854483: android-sdk: set default ANDROID_HOME

My understanding of that policy seems to be the opposite of yours. I think its saying that a package cannot set an env var, nor should it require that an env var is set in order to function. ANDROID_HOME is not required for things to function as far as I know.

Bug#854483: android-sdk: set default ANDROID_HOME

Package: android-sdk Version: 25.0.0+1 Severity: wishlist Dear Maintainer, as peer policy 9.9: "A program must not depend on environment variables to get reasonable defaults." https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.9 Please set ANDROID_HOME to /usr/lib/android-sdk/.