Related branches

Related bugs

Sprints

Whiteboard

I modified/extended the original wiki spec based on UDS discussion, and here is a dump of my UDS notes:

Packaging issues for Android on Ubuntu
======================================
packaging issues:
packaging of runtime
packaging of applications
rootfs issue for each user

runtime:
licensing apache2
requires own jre/classlibs
kernel support required
other components
will use std glibc?

apps:
packaging format different
how do we get android apps?
what about store?
to package natively as deb, backend would have to have android build
env also
there are default apps with android...
has basic dependencies for who can provide X svc...
convert/wrap packaged android (bin) apps into debs so we can handle
in existing apt-get backend infrastructure?

other issues:
we have system based app env vs proposed per user rootfs
netbook has no "users", hence per user rootfs not relevant
maybe apps can be stored/shared from one place, data per user dir
google emulator environment...lets not do anything that breaks it
first step android devkit/emulator support?

deployment:
applications/runtime shared, user data to be per home directory
runtime initially in ppa, relocate to archive karmic or karmic + 1
what to call it? uar (ubuntu-android-remix)?? :)
bzr / launchpad hosting runtime local changes, can upstream for git

questions:
what about android apps that also touch/have runtime components??
google appstore business arrangements?
investigate integration of android runtime and clutter
each android app has own effective userid...security model conflicts?