Redistributing Android SDK might break their Terms

[snoweuph]

RUN yes | sdkmanager --licenses \
    && sdkmanager "platform-tools" "build-tools;33.0.2" "platforms;android-33" "cmdline-tools;latest" "cmake;3.22.1" "ndk;25.2.9519653"

This might be against the Android SDKs Terms
https://developer.android.com/studio/terms

Some Lines Important to this:

Though the most concerning one is this one:

3.4 states:

You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK.

The Important Sentences are:

Except to the extent required by applicable third party licenses

and

you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK

As far as I understand, the Exception specified in it does not apply to this project and having the SDK downloaded into the Docker images, which are redistributed, is against their License Terms.

I wanted to put the Android SDK into some of my Dockerimages and noticed these parts in the Terms.

Would be cool to have somebody find a part in the Terms that actually allow redistributing it though :D
(I never thought the Terms were that restrictive before)

[Calinou]

This likely requires moving the Android SDK installation to the GitHub Actions export workflow that users use, so that the container image doesn't include the Android SDK. In short, we need to switch over to a "downloader" workflow, which will be less optimal and probably take more time to export (unless you never export to Android).

[snoweuph]

alternativley this project could directly ask google for a license to distribute it inside the docker

[Calinou]

alternativley this project could directly ask google for a license to distribute it inside the docker

Historically, this hasn't really happened to any other project in my experience. It's even less likely to happen for what is an unofficial Godot Docker image.