2199
Comment: first description of android versioms
|
2374
|
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`. | 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. |
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:
source package names are named after the git repository, prefixed by android- (e.g. android-platform-system-core, android-platform-system-extras, android-platform-build, android-platform-frameworks-base, etc.)
binary packages of utilities that run on Debian directly are named after the utility itself (e.g. zipalign, aapt, etc.)
shared libraries that are only used by android-tools packages are named after the library, without a ABI version number in the package name, and prefixed by android-. (e.g. android-libhost, android-libcutils-dev, etc.]] In the Google builds, these are built as static libraries, and linked statically into each binary. In the Debian builds, they are built as shared libraries and installed into /usr/lib/android.
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, 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.