On Sat, 2 Jul 2022 at 10:28, Tim Orling <[email protected]> wrote: >> 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. > 100% on board then. I will die on this mountain.
Ok, my brain couldn't avoid thinking about this, and so I have to write it out before there's any code, and thus invite more bikeshedding :) The way this will work is that there will be a command: $ bitbake-layers save-build-conf path/where name that will take the existing active configuration from build/conf and save it as a template in the specified location: path/where/name. Then 'bitbake-layers create-layer-setup' will refuse to proceed if it can't find any configuration templates in the active layers. meta-poky/conf that we all know and love and use daily doesn't count, but you can force the template-less setup with a command line switch if you so wish but no karma points for it. All template locations will be saved in the json metadata. Once the layer setup script is done setting up the layers, it can suggest a list of available configurations, and a command that you need to run to use one of them to set up a build. And if there aren't any, it will redirect concerns to the layer maintainers for not helping the layer users. Now this is getting somewhere, and that somewhere is more interesting than sticking with submodules, repo or kas :) Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#167547): https://lists.openembedded.org/g/openembedded-core/message/167547 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]] -=-=-=-=-=-=-=-=-=-=-=-
