On Fri, 2 Sept 2022 at 06:32, Alexander Kanavin via
lists.openembedded.org <[email protected]>
wrote:
> We can however add a hint to check what is in
> build/conf/templateconf.cfg if the test fails, as it is not obvious
> that TEMPLATECONF obtained from there takes priority over other
> sources (which are, in order, TEMPLATECONF passed via environment,
> then .templateconf next to oe-init-build-env).
Ok, the more I think about this, the more I'm convinced that
oe-setup-builddir needs a complete refactor. Specifically:
1. Let's rewrite it in python; shell just isn't expressive or readable
enough for what it needs to do.
2. Let's have a clear, logical priority order: TEMPLATECONF env var,
build/conf/templateconf.cfg, dirname('oe-init-build-env') +
'/.templateconf'
3. build/conf/templateconf.cfg becomes read-only; the final selected
value for TEMPLATECONF is written into a separate file (for having a
reference to where the configs came from).
4. oe-setup-builddir can also later be extended to support
'configuration fragments' management, see my email to oe-archtecture
from yesterday.
It's just too late to do this in this release cycle, but worth looking
into afterwards.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170236):
https://lists.openembedded.org/g/openembedded-core/message/170236
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]]
-=-=-=-=-=-=-=-=-=-=-=-
