W dniu 08.10.2015 o 12:37, Oliver Grawert pisze: > note that the android layer is equivalent to "device tarball", the > question is: will installs using this feature exist in a non snappy/non > touch context, note that in the snappy world *all* installs have a > device tarball (or soon device/kernel snap) that will in context of > phones ship the android container and in context of non android devices > still ship all device specific bits ... > > if we will ever only use a snappy or touch context, the device tarball > is the right place (though probably not actually an android property but > rather a simple text file we can bind mount into the rootfs, so we dont > have to manage special cases between android and non-android)... > > if it will actually be installed out of snappy/touch context we will > definitely need some different way ...
I think that other way is user-overrides, auto-detection and defaults, not much else we can do? Don't think we'll have per-hardware .debs shipping those. -- Michał Sawicz <[email protected]> Canonical Ltd.
signature.asc
Description: OpenPGP digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
