All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Draszik" <git@andred.net>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version)
Date: Wed, 30 Nov 2016 17:19:04 +0000	[thread overview]
Message-ID: <1480526344.13682.8.camel@andred.net> (raw)
In-Reply-To: <1480517999.6873.298.camel@intel.com>

On Wed, 2016-11-30 at 15:59 +0100, Patrick Ohly wrote:
> On Wed, 2016-11-30 at 14:31 +0000, André Draszik wrote:
> > On Wed, 2016-11-30 at 12:04 +0100, Patrick Ohly wrote:
> > > On Mon, 2016-11-21 at 12:03 +0000, André Draszik wrote:
> > > > This allows us to completely remove the build time
> > > > depenency on libcheck when not needed, reducing
> > > > overall build time, and in addition tests can be
> > > > converted into a PACKAGECONFIG to enable them if
> > > > needed.
> > > 
> > > +1
> > > 
> > > Sorry for the delay, I had to check with Joshua first who's going to
> > > merge your patches. I'm currently working on a major update of
> > > meta-swupd (see https://github.com/ostroproject/ostro-os/pull/198) and
> > > if there's enough interest for using it as part of Yocto, might
> > > continue
> > > maintaining it.
> > 
> > Thanks Patrick. Are you saying you would otherwise abandon meta-swupd
> > completely, or have it be a part of ostro-os only?
> 
> That's undecided. We are currently trying to figure out which update
> mechanism is a good fit for Yocto. Depending on the outcome of that and
> available resources, we may or may not have the time to support
> something.
> 
> I've started a Wiki page
> https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
> moment, but might as well be mentioned already now.
> 
> Perhaps you can say a few words about your usage of swupd and what you
> liked or didn't like about it? Note that performance will become better
> with the upcoming update.

In the wiki or here? I'll be out for the next week, but when I come back I
will write some more.

BTW, you probably know this: 
https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-May/002061.html

I liked swupd for its ability to be used both for initial provisioning as
well as for incremental updates. The latter being important when you have
*loads* of devices, where it doesn't seem to make sense to download a full
image for a tiny change to each device (think cellular!), the former
streamlining the update mechanism, so that not two different independent
things have to be maintained.


Cheers,
Andre'



  reply	other threads:[~2016-11-30 17:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 12:03 [meta-swupd][PATCH] bsdiff: update to latest version André Draszik
2016-11-30 11:04 ` Patrick Ohly
2016-11-30 14:31   ` André Draszik
2016-11-30 14:59     ` update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version) Patrick Ohly
2016-11-30 17:19       ` André Draszik [this message]
2016-12-01  7:42         ` Patrick Ohly
2016-12-01 10:26           ` André Draszik
2016-12-01 11:25             ` Patrick Ohly
2016-12-06  9:01       ` update mechanisms Stefano Babic
2016-12-06  9:45         ` Patrick Ohly
2016-12-06 14:11           ` Lopez, Mariano
2016-12-06 18:45             ` Philip Balister
2016-12-06 22:38               ` Stefano Babic
2016-12-07  7:05                 ` Kristian Amlie
2016-12-09 15:13                 ` Patrick Ohly
2016-12-09 16:03                   ` Stefano Babic
2016-12-12 14:59                     ` Mariano Lopez
2016-12-12 15:41                       ` Patrick Ohly
2016-12-12 15:49                         ` Mariano Lopez
2016-12-12 19:02                           ` Patrick Ohly
2016-12-13 14:03                             ` Lopez, Mariano
2016-12-12  6:39                   ` Kristian Amlie
2017-03-02  0:35                     ` Eystein Måløy Stenberg
2017-03-10 13:02                       ` Patrick Ohly
2017-03-10 13:35                         ` Kristian Amlie
2017-03-10 14:20                           ` Patrick Ohly
2016-12-13  8:51                   ` Mike Looijmans
2016-12-13  9:08                     ` Patrick Ohly
2016-12-12 15:13           ` André Draszik
2016-12-12 15:32             ` Patrick Ohly

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=1480526344.13682.8.camel@andred.net \
    --to=git@andred.net \
    --cc=patrick.ohly@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.