On Wed, 2016-02-24 at 15:40 -0500, Philip Balister wrote: > On 02/24/2016 02:51 PM, Paul Eggleton wrote: > > > > On Wed, 24 Feb 2016 11:35:25 Philip Balister wrote: > > > > > > On 02/24/2016 11:06 AM, Trevor Woerner wrote: > > > > > > > > Ideally the work done here and the work done on meta- > > > > swupdate[1] would > > > > be somehow merged so people creating images/distros would only > > > > have to > > > > learn and integrate one software update solution, instead of > > > > having to > > > > evaluate and choose between the two (or more?). > > > > > > > > [1] https://github.com/sbabic/meta-swupdate > > > Amen. I had the same thoughts reading the patch set intro. > > I think it would be hard to integrate these two, since they operate > > quite > > differently to eachother. > > > > > > > > Maybe the swupd should go in a seperate layer so we can see which > > > project works best for oe users before moving something directly > > > into > > > oe-core? > > This makes sense to me too though FWIW. The os-release patch should > > probably > > go straight in, but everything else looks like it could comfortably > > live in a > > separate layer without making things too difficult. > It also makes it easier to update as problems in swupd are resolved > since you do not need to go through the entire oe-core testing cycle.
I've pushed the series, including a couple of metadata fixes suggested in reply, as a layer here: http://git.yoctoproject.org/cgit/cgit.cgi/me ta-swupd/ Regards, Joshua -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
