[Merge] lp:~mfisch/ubuntu/saucy/ubuntu-touch-customization-hooks/add-scripts into lp:ubuntu/ubuntu-touch-customization-hooks

[Matthew Fischer]

1) /custom/etc/dconf/.updated => this will only happen once on the first boot, and then never again; why can't we pregenerate this in the image? dont you want to run this when custom.tgz is updated? Or perhaps you plan to remove the flag from the upgrade scripts once we have this support?

We cannot pre-generate it as the format of the dconf db depends on the version of dconf installed, so the build system and phone would have to match, which is probably impossible to enforce. We do plan on removing it when the tarball is updated.

2) I'm assuming you have some kind of server-side machinery that will prevent promotion of new base ubuntu.tgz when /etc/dconf/* changes in it, as for you to integrate the changes?

We only change /custom/etc/dconf, so this should not be an issue. We will prevent the custom tarball from updating anything in there, it needs to be an empty folder in the customized tarball, until the update is run.
-- 
https://code.launchpad.net/~mfisch/ubuntu/saucy/ubuntu-touch-customization-hooks/add-scripts/+merge/184880
Your team Ubuntu branches is subscribed to branch lp:ubuntu/ubuntu-touch-customization-hooks.