On Thu, 2024-05-09 at 18:08 +0200, Alexander Kanavin via lists.openembedded.org wrote: > From: Alexander Kanavin <a...@linutronix.de> > > This allows fine-tuning local configurations with pre-frabricated > configuration snippets in a structured, controlled way. It's also > an important building block for bitbake-setup. > > There are three operations (list/add/remove), and here's the list output: > > alex@Zen2:/srv/storage/alex/yocto/build-64$ bitbake-config-build > list-fragments > NOTE: Starting bitbake server... > Available fragments in selftest layer located in > /srv/work/alex/poky/meta-selftest: > > selftest/test-another-fragment This is a second configuration fragment > intended for testing in oe-selftest context > selftest/test-fragment This is a configuration fragment intended for > testing in oe-selftest context > > The tool requires that each fragment contains a one-line summary > at the top, followed by multiple lines of description, as hash-prefixed > comments. > > Signed-off-by: Alexander Kanavin <a...@linutronix.de>
Firstly, thanks for putting this together, I'm very much in favour of adding something like this. The main questions I have are around the interface and naming. My feedback/open questions: a) I'm not totally sold on "bitbake-config-build" as the command name. I will give that a bit more thought. b) The code adding/removing require lines from local.conf seems a little fragile. I did wonder if we wanted a higher level bitbake API to this, for example a BB_CONF_FRAGMENTS variable which basically tagges a set of config files onto the end of the base configuration parsing? This wouldn't be hard to implement in bitbake and would then make the tooling easier and less fragile. c) Do we want to have the config fragment name as a "<layername>/<fragementname>" pair and have the fragments live directly in conf/fragments in a layer? d) How do you control ordering between the fragments? Do we need dependencies? How does layer ordering or dependencies affect anything? Can fragments conflict? e) You've used comments at the start of the files as summary/description. Should we use some kind of more variable like syntax which allows for other information in the future? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#200468): https://lists.openembedded.org/g/openembedded-core/message/200468 Mute This Topic: https://lists.openembedded.org/mt/106004166/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
