From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) by mail.openembedded.org (Postfix) with SMTP id 59FC977330 for ; Wed, 24 Feb 2016 20:40:35 +0000 (UTC) Received: (qmail 4470 invoked by uid 1003); 24 Feb 2016 20:40:36 -0000 Received: from unknown (HELO ?192.168.11.140?) (philip@opensdr.com@71.171.13.83) by mail.geekisp.com with (DHE-RSA-AES128-SHA encrypted) SMTP; 24 Feb 2016 20:40:36 -0000 To: Paul Eggleton , openembedded-core@lists.openembedded.org References: <56CDD519.9050109@gmail.com> <56CDDBCD.6090303@balister.org> <2791977.VXU03QmIbh@peggleto-mobl.ger.corp.intel.com> From: Philip Balister Message-ID: <56CE1543.7050703@balister.org> Date: Wed, 24 Feb 2016 15:40:35 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <2791977.VXU03QmIbh@peggleto-mobl.ger.corp.intel.com> Cc: Joshua Lock Subject: Re: [PATCH 00/10] Integrate swupd software updater X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2016 20:40:36 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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. Philip > > Cheers, > Paul >