touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #26678
[Bug 1203800] Re: [MIR] Android, CyanogenMod, Clockworkmod, et al
** Changed in: android (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1203800
Title:
[MIR] Android, CyanogenMod, Clockworkmod, et al
Status in “android” package in Ubuntu:
New
Status in “android-src-vendor” package in Ubuntu:
New
Status in “android-tools” package in Ubuntu:
Fix Released
Status in “gcc-arm-linux-androideabi” package in Ubuntu:
New
Bug description:
Availability:
* ppa:ubuntu-toolchian/android and/or saucy/multiverse
Rationale:
* needed to build http://cdimage.ubuntu.com/ubuntu-touch/
Security:
* see include copies of code
* upstream, infrequent OTA updates / code-drops with/without security patches
QA:
* package not-trivial to build, sources prepared using repo forest checkout
* upstream is mostly health and actively takes patches (AOSP & Cyanogenmod)
* these builds are for exotic hardware (nexus *) which require binary blobs for support
Dependenices:
* cross-toolchain and packages are self-contained to compile from source for arm-linux-androideabi
* Using sbuild, it builds correctly in i386 chroots, to build on amd64 hosts the package:i386 need to be installed, as the build is done using multilib toolchain targetting 32bit. Limitations in sbuild/current mutliarch spec doesn't allow speficying package:i386 [amd64] build-dependencies
Standards compliance:
* the packages comply with FHS, but by themself are not very useful, as in the end one should use android-tools to flash the produced binareis onto target devices
Maintainance:
* Ubuntu and Phone Foundations teams are maintaining these set of packages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1203800/+subscriptions