On Wed, 28 Sept 2022 at 16:25, Peter Kjellerstedt <[email protected]> wrote:
> Personally, I would expect the file to contain the latest value used > for TEMPLATECONF. I.e., if I remove the local.conf file to regenerate > it because there has been upstream changes, I would expect it to use > the TEMPLATECONF I specify at that time, and for that value to be > recorded for posterity. > > That said, I doubt the value of TEMPLATECONF will actually change for > an existing build environment, so this is probably more on the > theoretical side. This would complicate the logic (update only if some config was updated), and if you remove local.conf but not bblayers.conf, so that one is updated, but not the other, it is not anymore possible to tell what came from where. Creating it once at the start is more straightforward, even if origins of further updates are not recorded. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1653): https://lists.openembedded.org/g/openembedded-architecture/message/1653 Mute This Topic: https://lists.openembedded.org/mt/93968540/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
