On Mon, Oct 19, 2015 at 11:27 PM, Fabrice Desré <[email protected]> wrote: > On 10/19/2015 07:55 PM, Jonas Sicking wrote: >> On Mon, Oct 19, 2015 at 6:39 AM, Christopher Lord <[email protected]> wrote: >>> So currently it's built with the rest of the system, I don't know what >>> implications that has for updating... We could distribute it as a >>> marketplace app I think? Unfortunately got too many other things to deal >>> with right now to investigate this, but if anyone does, I'm sure it'd be >>> appreciated. >> >> At the very least we need to make sure that the app gets updated when >> we do a system update. For example when we're rolling out a new >> Foxfooding build. It would be sad if users and foxfooders got stuck on >> an old version of the homescreen. >> >> Fabrice probably knows what does and does not get updated. > > The closest case we have now is marketplace which is also packaged. The > difference is that the marketplace app is not part of gaia itself and > thus is built out of band. The marketplace team then commit the > pre-built package directly and the metadata we need (like the hash of > the manifest and the package, and the url of the update manifest). > It seems like we would need a slightly different flow for the homescreen > if we want to keep building in as part of gaia *and* publish it to the > marketplace. My secret hope was to get nsec packages ready instead of > doing that!
Some critical parts of nsec will not land for 2.5. Such as the ability to ensure that a package is cached and doesn't need to be loaded from network. This is quite critical for the homescreen since you don't want it to stop working if you are offline :) Sounds like one solution here is to not put the homescreen in marketplace for now. / Jonas _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
