about generation of sw-versions

[asura]

hi：

2 ways to generate sw-versions

1. Embedded in the swu package as a file resource

2. Write its own version information to the sw-versions file when the corresponding program module is running

What method is generally recommended?

I prefer option 2, but if the swu upgrade package packs multiple application modules to be upgraded, how do you handle multiple applications writing their version information to the same swu-versions file?

Thanks, looking forward to replying.

[Stefano Babic]

Hi Asura,

On 25.11.23 04:10, asura wrote:
> hi：
> 2 ways to generate sw-versions
> 1. Embedded in the swu package as a file resource

IMHO the version of an artifact should be bound into the artifact to
enhance consistency. That is, version of bootloader should be read from
the bootloader, version of the kernel from the kernel, etc.

Adding a file with version is weak.

> 2. Write its own version information to the sw-versions file when the
> corresponding program module is running
> What method is generally recommended?
> I prefer option 2, but if the swu upgrade package packs multiple
> application modules to be upgraded, how do you handle multiple
> applications writing their version information to the same swu-versions
> file?

Yes, second option. You can also have a service / something running at
boot and populating the /etc/sw-versions file by analyzing / reading
information from each of the modules (artifacts you want to change)


Best regards,
Stefano Babic

--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================