Differences between revisions 4 and 5
Revision 4 as of 2014-10-07 14:52:18
Size: 2374
Comment:
Revision 5 as of 2014-10-07 15:03:46
Size: 3326
Comment: android versioning madness
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
There are many [[https://source.android.com/source/build-numbers.html|naming]] [[https://en.wikipedia.org/wiki/Android_version_history|schemes]] for versions in Android, and none are used everywhere. For the Android OS itself, there are three schemes: version names, like ''Gingerbread'' or ''Kitkat''; version numbers, like 2.3.7 or 4.4.2; and, SDK version numbers, like `android-10` or `android-19`. None of these line up with each other. For example, the ''Jelly Bean'' name spans 4.1 through 4.3.1 and `android-16` through `android-18`. The version numbers and SDK numbers also do not line up, with `android-14` covering 4.0.1 - 4.0.2, `android-15` covering 4.0.3 - 4.0.4, but `android-16` covers all of 4.1.x. There are many [[https://source.android.com/source/build-numbers.html|naming]] [[https://en.wikipedia.org/wiki/Android_version_history|schemes]] for versions in Android, and none are used everywhere. For the Android OS itself, there are three schemes: version names, like ''Gingerbread'' or ''Kitkat''; version numbers, like 2.3.7 or 4.4.2; and, "API level" numbers, like `android-10` or `android-19`. None of these line up with each other. For example, the ''Jelly Bean'' name spans 4.1 through 4.3.1 and `android-16` through `android-18`. The version numbers and API level also do not line up, with `android-14` covering 4.0.1 - 4.0.2, `android-15` covering 4.0.3 - 4.0.4, but `android-16` covers all of 4.1.x.

The madness doesn't end there. Next up we have SDK version numbers, which are like 20, or 23.0.2. Part of the SDK includes the `build-tools` package, which has its own version numbers, which are like 18.1.1 and 20.0.0, but these do not line up with the SDK version numbers. The `platform-tools` seems to have its own versioning scheme also, but it is not really exposed. Then there are the NDK release numbers, which are like `r8b` or `r10`, and they also do not line up with anything else.

In the git repo, there are a mishmash of tags and branches that do not represent all of these various versions. There does seem to be consistent tagging of the OS releases, you can see those listed under [[https://source.android.com/source/build-numbers.html|Source Code Tags and Builds]]. There are a few branches that seem to line up to the SDK version numbers, like `tools_r21` and `tools_r22.2`, but there is not a complete set of those branches.

This page is a gathering place for information about the android-tools packaging team, which is focused on packaging the Android development tools for Debian. There are also some packages which help run Debian in a chroot on Android.

Package naming scheme

The naming scheme for android-tools packages is as follows:

Android's upstream version names

There are many naming schemes for versions in Android, and none are used everywhere. For the Android OS itself, there are three schemes: version names, like Gingerbread or Kitkat; version numbers, like 2.3.7 or 4.4.2; and, "API level" numbers, like android-10 or android-19. None of these line up with each other. For example, the Jelly Bean name spans 4.1 through 4.3.1 and android-16 through android-18. The version numbers and API level also do not line up, with android-14 covering 4.0.1 - 4.0.2, android-15 covering 4.0.3 - 4.0.4, but android-16 covers all of 4.1.x.

The madness doesn't end there. Next up we have SDK version numbers, which are like 20, or 23.0.2. Part of the SDK includes the build-tools package, which has its own version numbers, which are like 18.1.1 and 20.0.0, but these do not line up with the SDK version numbers. The platform-tools seems to have its own versioning scheme also, but it is not really exposed. Then there are the NDK release numbers, which are like r8b or r10, and they also do not line up with anything else.

In the git repo, there are a mishmash of tags and branches that do not represent all of these various versions. There does seem to be consistent tagging of the OS releases, you can see those listed under Source Code Tags and Builds. There are a few branches that seem to line up to the SDK version numbers, like tools_r21 and tools_r22.2, but there is not a complete set of those branches.