On Tue, 5 Jul 2022 at 10:51, Richard Purdie <[email protected]> wrote:
> As for kconfig, I don't think we need another config file format. I > have proven that json can encapsulate all the complexities of the > configurations of the autobuilder and kas has also proven the same > think with yaml. Yes, the menus are nice but at some point users will > need to see our config files so I don't think its a much of a win as > people think, unless the entire project used it which it doesn't and is > unlikely to. What is more important to me is that each machine, distro and templateconf comes with a *description* right next to the actual .conf file. They all must have conf-notes.txt, and that should be a requirement for YP compatibility actually. Then if anyone wants to write a tool that discovers the available items and presents a UI for choosing them, the documentation for each of the item is already in place and not maintained separately (which inevitably results in things getting out of sync). Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#167646): https://lists.openembedded.org/g/openembedded-core/message/167646 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]] -=-=-=-=-=-=-=-=-=-=-=-
