On Fri, 2 Sept 2022 at 16:47, Peter Kjellerstedt <[email protected]> wrote:
> The expectation is of course that if one has one's own .templateconf > file, then it will of course have to be updated to match the changes > in OE. Nothing unusual with that. But that is something I do as > maintainer of our environment. For our developers it will then just > work. Please consider that there are three different ways to obtain the location of the template, and they must all work. For those who have created a build/conf by supplying TEMPLATECONF on the command line or templateconf.cfg (which I would say is everyone, except you) the suggested code will only make things worse, not better. It would take wrong but helpful value in templateconf.cfg that points to a custom template, and replace it with meta/conf/templates/default, because that is what they have in .templateconf. Then all trace of where the template came from is lost. And as discussed previously, you don't even need to jump through the extra hoops with generated template configurations to begin with, and can write the dynamically generated configs directly into build/conf. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#170254): https://lists.openembedded.org/g/openembedded-core/message/170254 Mute This Topic: https://lists.openembedded.org/mt/93396426/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
