mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe via RAUC" <rauc@pengutronix.de>
To: Brian Hutchinson <b.hutchman@gmail.com>, rauc@pengutronix.de
Subject: Re: [RAUC] Is it possible to change the [system]compatible= string after it has already been set/flashed?
Date: Fri, 06 Dec 2024 10:25:16 +0100	[thread overview]
Message-ID: <42177c2c425f7b240c65e41d6b6a4aac7b5b5ab1.camel@pengutronix.de> (raw)
In-Reply-To: <CAFZh4h9tu5WLxbAnA76iZ0+R5B1Oog89xeMN4-gWuBch7OPVSQ@mail.gmail.com>

On Thu, 2024-12-05 at 22:38 -0500, Brian Hutchinson via RAUC wrote:
> Hi,
> 
> Since it's common to produce boards with pre-programmed flash etc., is
> it possible to change the [system]compatible= string when hardware
> changes happen and the compatible string needs to be updated when it
> has already been set previously?
> 
> I know that hooks could be used to key in on bundle version
> information to implement things like downgrade barriers etc., but it
> just feels more elegant to update the compatible string to describe
> hardware changes that are human readable than to keep up with a eye
> chart truth table of version number combinations to determine what is
> safe to downgrade, upgrade etc.
> 
> I was thinking if maybe [system]variant-file was used in system.conf,
> then a pre-install hook could easily manipulate the compatible string,
> but not sure that would work.
> 
> This almost feels like the intermediate update that's necessary with
> changing rauc versions ... but I searched the mail archives and
> couldn't find anyone wondering about this sort of thing so thought I'd
> ask Jan, Enrico & Co. their thoughts.

You can use a 'install-check' hook [1] in the bundle to override the normal
compatible check. 

Also, the variant handling is built in a way so that you can start setting the
system variant in new systems that behave differently and you can target the
different images correctly.

Regards,
Jan

[1] https://rauc.readthedocs.io/en/latest/using.html#install-hooks

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2024-12-06  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  3:38 Brian Hutchinson via RAUC
2024-12-06  9:25 ` Jan Lübbe via RAUC [this message]
2024-12-09  8:43 ` Jan Lübbe via RAUC

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=42177c2c425f7b240c65e41d6b6a4aac7b5b5ab1.camel@pengutronix.de \
    --to=rauc@pengutronix.de \
    --cc=b.hutchman@gmail.com \
    --cc=jlu@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