mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Matt Campbell <mcampbell@izotope.com>, rauc@pengutronix.de
Subject: Re: [RAUC] Backwards/forwards compatibility of bundle format
Date: Fri, 05 Jun 2020 08:24:58 +0200	[thread overview]
Message-ID: <0acb7ca57dc256c3149a5426af8dc39350b9cbd8.camel@pengutronix.de> (raw)
In-Reply-To: <CAMDowVVbSDM+BAJoksBTqN7oy6frsm0Oo16wB8Wg5Uupe0Q_LQ@mail.gmail.com>

Hi,

On Thu, 2020-06-04 at 15:02 -0400, Matt Campbell wrote:
> I'm looking into RAUC for a product, and I was wondering if there are
> any project goals around the stability of the RAUC bundle format.
> Specifically, it would be great if all future versions of the rauc
> binary was compatible will all previous bundle formats, and also that
> all older versions of the binary can install future created bundles.
> Obviously that's a big ask, but it'd be great to know what to expect
> of RAUC in the future. Even a rough idea of how compatibility will 
> play out will help me greatly in evaluating RAUC.

The basic bundle format has not changed so far (squashfs with 
CMS
signature), which means that newer versions can install old bundles.
Going forward, any issue with installing old bundles would be
considered a bug.

Newer RAUC versions have introduced new features and slot types, though
(such as casync, emmc-boot partitions, MBR partition switching). If you
use those features, old versions of RAUC won't be able to install those
bundles. As long as you don't use new features, our intention is that
bundles created by newer versions will be installable by older
versions.

There are ideas of introducing a new bundle format to allow streaming
installation (over the network), but we won't remove support for the
original format.


If there are ever reasons that require an incompatible change, you can
use a two step migration:
You can use an intermediate update to ship a new RAUC binary in a
bundle created by the old version. Then use the newly installed RAUC
for the real update.


Does that answer your questions?

Regards,
Jan


_______________________________________________
RAUC mailing list

  reply	other threads:[~2020-06-05  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 19:02 Matt Campbell
2020-06-05  6:24 ` Jan Lübbe [this message]
2020-06-05 20:30   ` Matt Campbell

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=0acb7ca57dc256c3149a5426af8dc39350b9cbd8.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=mcampbell@izotope.com \
    --cc=rauc@pengutronix.de \
    /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