-----Original Message-----
From: cip-dev@... <cip-dev@...> On Behalf
Of Jan Kiszka
Sent: 01 February 2023 13:06
To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
tsip.com>; cip-dev@...
Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
<kazuhiro3.hayashi@...>
Subject: Re: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf
using placement of kas file wic-targz-img.yml

On 31.01.23 17:55, Venkata.Pyla@... wrote:

Hi,

I am trying to overwrite the IMAGE_FSTYPES variable with the values in wic-

targz-img.yml by keeping at the end in kas file definition as shown in below
command, but it is not overwriting.

$ kas-container build
kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml

kas/opt/ebg-swu.yml include local_conf_header as below
-----------------------------------------
local_conf_header:
...
wic-swu: |
...
IMAGE_FSTYPES = "wic"
...
-----------------------------------------


kas/opt/wic-targz-img.yml include local_conf_header as below
-----------------------------------------
local_conf_header:
...
image-type: |
...
IMAGE_FSTYPES = "wic tar.gz"
...
-----------------------------------------

Final conf/local.conf generate as below
-----------------------------------------
# image-type
IMAGE_FSTYPES = "wic tar.gz"

...

# wic-swu
IMAGE_FSTYPES = "wic"
-----------------------------------------


Expecting conf/local.conf
-----------------------------------------
# wic-swu
IMAGE_FSTYPES = "wic"

...

# image-type
IMAGE_FSTYPES = "wic tar.gz"
-----------------------------------------

The above is possible when I use name with higher in alphabetical
order like 'zimage-type:' in the wic-targz-img.yml
kas/opt/wic-targz-img.yml with
-----------------------------------------
local_conf_header:
...
zimage-type: |
...
IMAGE_FSTYPES = "wic tar.gz"
...
-----------------------------------------

Is this the only solution to set the order of the variable assignment in

local_conf_header?

local.conf nodes are alphabetically sorted as you already found out - we should
probably document that in kas. Generally spoken, you can make use of that to
achieve append behaviour, or you overwrite the original node you are
competing with.

In case of isar-cip-core, we can rearrange or kas option files so that your use
case becomes possible (though I'm unsure if it makes any sense:
the content of the tar.gz will be only a subset of the wic swupdate image).

Thanks for confirming,
I want to create swupdate image that should generate both tar.gz and wic image and use tar.gz for reproducibility checks.

I probably have to modify this file kas/opt/swupdate.yml to include both in IMAGE_FSTYPES = "wic tar.gz".

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux