baltpeter
commented
1 week ago Not using the $ANDROID_HOME was a deliberate decision. I feel like automatically changing/installing packages in $ANDROID_HOME without prompting the user would be quite "rude", but that's exactly what andromatic is supposed to do in the context of the Tweasel tools.
I could see andromatic being more useful for other use cases, though, if there was an option to alternatively use an existing directory, as you also propose. I think implementing that would be a good additional feature.
However, I'm not quite sure how that would look given the current API. Since all of the functions stand on their own, we don't really have anywhere we could add this option…
Hi,
I would like to suggest a feature that would allow Andromatic to utilize preinstalled SDK tools such as sdkmanager, platform-tools, and cmdline-tools.
To achieve this, Andromatic could first check for the required tools in the $ANDROID_HOME directory before proceeding with any installations. Additionally, it could accept the installation path as an argument, with automatic installation serving as a fallback option.
For instance @wtto00/android-tools uses the first two options.
It would be beneficial from a security perspective to have the option to control the installation process manually, rather than allowing Andromatic to automatically download and install binaries (including Java) in the background.
While I like that the current approach simplifies the installation process by eliminating the complexities of manual setup, it would be great to provide users with the choice of how the tools should be installed.