For future enhancements, I would want to keep some kind of record inside build/conf of where the original template was taken from. I agree that build init scripts should not use it at all, but that record can be utilized to either update the build config from an updated template (with an explicit, separate command), or update the template itself without having to specify where it is.
Alex On Wed, 28 Sept 2022 at 10:42, Richard Purdie <[email protected]> wrote: > > I'm starting a new thread/discussion on this with a new perspective. > > I did a little research myself on how these files are being used. My > conclusion is that templateconf.cfg isn't really used by much at all > other than to decide whether to rerun setup pieces. > > I'm going to make the assumption that once a build directory is setup, > the user does not want the env setup scripts messing with it again. If > they did, they'd start a new build directory. > > As such: > > a) showing the user a warning about the template locations changing is > probably not necessary > b) reading the value back in from templateconf.cfg isn't then necessary > as either the files don't exist and we set then up or we don't care > > Therefore, my thinking is that we should simply remove > templateconf.cfg? > > What am I missing? > > Cheers, > > Richard >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1649): https://lists.openembedded.org/g/openembedded-architecture/message/1649 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]] -=-=-=-=-=-=-=-=-=-=-=-
