ubuntu-phone team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

hi
Am Donnerstag, den 16.01.2014, 18:16 -0800 schrieb Steve Langasek:

> > even if we ship them in the android tarball (which as i mentioned
> > elsewhere is a lot more effort to rebuild for a single change), they
> > have to live in the rootfs after all.
> 
> In fact, we already patched udev once to look at picking up firmware files
> from /vendor/firmware and /system/firmware before we decided this wasn't
> actually necessary (and even harmful, because we didn't want udev loading
> firmware if ueventd had already loaded it).  And we've even talked about
> autogenerating udev rules from ueventd blocks (though this seems to have
> stalled with me for quite a while... sorry about that).  I see no reason we
> couldn't / shouldn't add /vendor/udev/rules.d, or even /run/udev/rules.d, to
> the udev path to handle device-specific rules in a way that preserves our
> hardware-independent, read-only rootfs.
> 
building the android package takes around 1h and requires you to
download a ~250MB source package, building lxc-android-config takes 2
minutes and requires you to download 25KB and it allows you to use the
established merge proposal process via launchpad while changes to the
android package have to be made to the phablet.ubuntu.com git tree (not
sure if our gerrit instance is already up but up to now the only way to
get patches included was by mailing someone who can commit to the git
tree (or respectively the ML)... 

doing development and testing a change to a device permission locally
before uploading is proportionally a lot harder with the android
package ... i would like to keep the changes as long as possible in the
lxc-android-config package, even if we decide they should live inside
the android package at some point ...

ciao
	oli

Attachment: signature.asc
Description: This is a digitally signed message part