hi, Am Dienstag, den 04.03.2014, 19:56 +0200 schrieb Jani Monoses: > I also agree the Android build tree should have these even though they > belong to the Ubuntu filesystem. The main reason is I am sure most > OEMs (and even some of us) prefer copying a few files around and have > as direct control over them as possible vs. building a .deb just for > them with all the PPA/image build hooks/hack-to-deploy cycle latency. > In this custom case the elegance of having source packages is trumped > IMHO by pragmatism. > One way of doing it is having them set as part of the install and > upgrade steps. For the BQ we now unpack the Ubuntu zip and then have a > script adb push over the dev specific files to the Ubuntu root. So it > does not need to be bind mounted or copied at Ubuntu boot time, no > Ubuntu side logic is needed. Something similar needs to be hooked into > the system image upgrade, so they do not get lost. Again, I agree this > is not very elegant, but seems the one that most 3rd parties could get > on board with as it requires almost 0 Ubuntu dev specific knowledge. > we discussed this on IRC today and came to teh agreement to discuss it at a vUDS ... i will register a UDS slot for it and prepare a list with all device specific files we ship today prior to the session ... just moving the stuff over on first boot or bind mount it is not a problem but we'll need to put some mechanics in place that do this properly survive upgrading etc ... and there are some bits that better should live upstream (alsa and pulse configurations and profiles for example ... bluetooth needs some more thnan just copying files over etc etc)
i'll subscribe everyone who spoke up in this thread to the blueprint
(and will publish the url here as well)
ciao
oli
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
