ubuntu-phone team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

On Tue, Jan 14, 2014 at 02:46:38PM -0800, Alex Chiang wrote:
> >> While this works for now with our limited set of supported devices, it can
> >> quickly become untenable once we start building images for OEMs in the future,
> >> or if we get an influx of community builds.

> > I figured that a necessary part of building up the port was building up the udev
> > rules and apparmor accesses. OEMs/community builds would either fork
> > lxc-android-config or work within the existing hierarchies to ship files in the
> > appropriate directories. Both are shipped as debs and depart from the "one
> > rootfs image for all devices" goal of course.

> Speaking with Steve Langasek yesterday, I got strong guidance that all
> per-device configs really need to live in the customization tarball.

Per-device changes in the device tarball; per-carrier changes in the
customization tarball.  Sorry if I wasn't clear.

> And the customization tarball is only allowed to drop files into
> /custom and $HOME.

Right; the paths change for customization vs. device tarball, but as per my
previous message, the fundamental constraint ("don't try to change files on
the rootfs") doesn't.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@xxxxxxxxxx                                     vorlon@xxxxxxxxxx

Attachment: signature.asc
Description: Digital signature