On Sat, 2 Jul 2022 at 07:58, Tim Orling <[email protected]> wrote: > One remaining question is how do we handle configuration? This seems to > address manifest?
Configuration will be handled with TEMPLATECONF and a set of templates in a product/platform layer. It's already in core, it's simple to understand and it works. We used it in a very large project. It also requires a certain bit of discipline, which is a good thing: you don't get to implement ugly local.conf hacks in a turing complete language, and must design your configuration (distro, machines and images) carefully in a static manner. Then local.conf must contain only DISTRO and MACHINE, and a 'confuguration' is essentially a choice of those two plus a set of enabled layers plus site-specific settings for sstate, downloads, proxies and parallelism level. Back to (maintainable) basics. And yes, I didn't want to open a discussion about this, I even didn't describe upfront how I'm going to do this to a customer who's supporting the work (if said customer is reading this, I appreciate the trust). I simply sat down and wrote the code. The principle is: make a tool that fits in a single commit and that I would want to personally use. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#167545): https://lists.openembedded.org/g/openembedded-core/message/167545 Mute This Topic: https://lists.openembedded.org/mt/92117681/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
