From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Philip Balister <philip@balister.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/10] Integrate swupd software updater
Date: Thu, 25 Feb 2016 21:42:23 +0000 [thread overview]
Message-ID: <1456436543.13135.7.camel@linux.intel.com> (raw)
In-Reply-To: <56CE1543.7050703@balister.org>
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
prev parent reply other threads:[~2016-02-25 21:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 14:52 [PATCH 00/10] Integrate swupd software updater Joshua Lock
2016-02-24 14:52 ` [PATCH 01/10] rsync: add native variant Joshua Lock
2016-02-24 14:52 ` [PATCH 02/10] swupd-server: initial recipe 2.53 Joshua Lock
2016-02-25 8:11 ` Maciej Borzecki
2016-02-25 8:51 ` Joshua G Lock
2016-02-24 14:52 ` [PATCH 03/10] hardlink: add new recipe Joshua Lock
2016-02-24 21:00 ` Burton, Ross
2016-02-24 22:57 ` Andre McCurdy
2016-02-25 8:48 ` Joshua G Lock
2016-02-25 17:13 ` Mark Hatle
2016-02-25 21:40 ` Joshua G Lock
2016-02-25 21:57 ` Mark Hatle
2016-02-24 14:52 ` [PATCH 04/10] swupd-client: Add recipe Joshua Lock
2016-02-25 8:07 ` Maciej Borzecki
2016-02-25 8:50 ` Joshua G Lock
2016-02-24 14:52 ` [PATCH 05/10] swupdbundle: new class to generate virtual images for swupd-image Joshua Lock
2016-02-25 8:19 ` Maciej Borzecki
2016-02-25 8:47 ` Joshua G Lock
2016-02-25 17:06 ` Patrick Ohly
2016-03-01 13:45 ` Joshua G Lock
2016-02-24 14:52 ` [PATCH 06/10] swupd-image.bbclass: initial class to support swupd updater Joshua Lock
2016-02-24 14:52 ` [PATCH 07/10] oe-swupd-helpers: provide swupd-client required helper scripts and units Joshua Lock
2016-02-24 14:52 ` [PATCH 08/10] swupd-client: RDEPENDS on oe-swupd-helpers Joshua Lock
2016-02-24 14:52 ` [PATCH 09/10] swupd-client: enable native builds Joshua Lock
2016-02-24 14:52 ` [PATCH 10/10] os-release: sanitise VERSION_ID field Joshua Lock
2016-02-24 15:37 ` [PATCH 00/10] Integrate swupd software updater Patrick Ohly
2016-02-24 16:14 ` Joshua G Lock
[not found] ` <1456330147.5333.14.camel@intel.com>
2016-02-24 18:49 ` Patrick Ohly
2016-03-01 16:18 ` Joshua G Lock
2016-02-24 16:06 ` Trevor Woerner
2016-02-24 16:35 ` Philip Balister
2016-02-24 18:36 ` Maciej Borzecki
2016-02-24 19:51 ` Paul Eggleton
2016-02-24 20:40 ` Philip Balister
2016-02-25 21:42 ` Joshua G Lock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456436543.13135.7.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=philip@balister.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox