I think this can be fixed with a patch that you can propose? E.g. change the logic to first copy conf-notes.txt into the build dir with the same conditions as local.conf.sample, then display it out of the build dir.
Alex On Sun, 11 Jun 2023 at 16:06, <[email protected]> wrote: > > Hi, > > Sorry for the duplicate answer, for those who received the first one, but I > messed up with the recipients. > > Actually, this file templateconf.cfg is used when entering an existing build > directory to display the template conf-notes.txt. Indeed, I noticed the > changed you made because now, when entering my build directory, it does not > show the custom notes, but always the default ones. > > Maybe you’re right writing that keeping the template source is useless, but > if so, we should probably copy the conf-notes.txt along when creating a new > build directory, so that it can be displayed again when coming back. > Otherwise, is it possible to revert the change? > > Regards, > > Stéphane. > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1711): https://lists.openembedded.org/g/openembedded-architecture/message/1711 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]] -=-=-=-=-=-=-=-=-=-=-=-
