ubuntu-phone team mailing list archive

[John McAleely <john.mcaleely@xxxxxxxxxxxxx>]

On 17/01/14 16:38, Oliver Grawert wrote:

> our whole system is currently designed around the android lxc container
> and libhybris for hardware interaction, once something else comes around
> we can indeed change this (but will also need to change code), for now i
> would say hardware support equals the android zip/container (even our
> install process requires a modified android recovery)

Without a clear path to being device-specifc-but-not-android, I think we
we push our 'common parts' to take the approach that they are aggregated
sets of all the settings needed for all devices.

That might be fine while we are one team, managing a handful of public
devices, even if it clearly seeds a long term problem.

It only takes one file to need to be device-specific, and also
confidential-before-launch to require the 'common parts' bundle to be
forked/patched in some way.

I think that is a genie we would rather not let out of the bottle. As
you note, there are already 7 cases where device specifics are needed. I
assume that as we gain more devices, that number will grow, even if we
also act to add generic abstractions into the common parts to manage
those device specifics.

J

Attachment: signature.asc
Description: OpenPGP digital signature