As part of the multipleupdates being made to the androidenv packages by @hadilq and others recently, we’re changing our policy to match that of the BEAM ecosystem: all packages will now track the latest versions by default unless you want a particular version of the SDK tools, which you can still select as usual.
The Android SDKs suffer from a lot of version churn, resulting in a lot of manual labor to update the versions stored in nixpkgs. We are supplementing the new policy with automation: we’re soon to have automatic updates and test suite runs so we never miss a version.
If you’re interested in reviewing the implementation, here’s the PR. We hope to have more updates for you in the future as we try to better modernize the Android part of nixpkgs.
An update on this: all Android SDK packages will soon be indexed by https://search.nixos.org, under androidenv.androidPkgs.all.*. The autoupdate will track the latest on unstable.
The following is an unpaid advertisement from the Nixpkgs Association For Unvendoring Google Code:
Does trying to extract anything from Google’s nigh-impenetrable set of Git monorepos fill you with excitement? Maybe you’d like to get ChromeOS’ update-engine building in Nix, or just want NixOS running on the ShiftPHONE 8, as @matthewcroughan and I got working at SCaLE 22x.
Well, did you know that nixpkgs contains a version of Android Studio that Google releases for Android platform development, instead of just for apps? How about packaging the Android NDK in a way that supports Android cross compilation from nixpkgs?
If you’re interested in taking these or other Android-related things on, submit a PR adding yourself to the Android team list today!
Note: Most build closures are multiple gigabytes large. The Android team is not responsible for any SSD wear-related incidents that are a result of downloading Android SDK packages.