Thank you for the reply. 

 

In Scarthgap LTS implementation is different, but I got the idea. 

 

I believe default behavior should be same as before to persist /var/temp over reboot and these changes should only be required for any customization. Also somewhat difficult for us to upgrade CI/CD with this config. 

 

Can we know the reasons for original changes here?

 

I reviewed commit message but not giving much details. Considering default base-files and as persistence is required, this newer approach seems be an issue. 

 

We recently migrated to Scarthgap and noticed the issues with our system. This can be issue for other developers as well whoever is planning to migrate to Scarthgap and embedded devices in the field. This commit requires all build systems to adopt changes bitbake.conf which is not preferable .  

 

What is the usecases targeted with the changes? I believe the commit should be reviewed again and potentially reverted considering default behavior with base-files and 00-create-volatile.conf.

 

 

 

Regards,

VS.