The qemuboot.conf uses configparser which can't suport upper case as key, and json is more clearer than configparser and is widely used in oe-core, so use qemuboot.json to replace qemuboot.conf.
Hi Robert, I'm willing to make this change if no one is currently implementing it. Should backward compatibility be kept with qemuboot.conf? `runqemu` seems to accept qemuboot.conf configuration files as an argument, so is changing this to support only json configuration files considered a breaking change (or is that not a major concern?). Thanks!
Guillaume, thanks. If no one responds here, try sending an RFC email to the list.
Hi Randy, thank you for your answer. I ended up sending an RFC on the mailing list a month ago, but it seems that this bugzilla report was not answering to any real world need, so the discussion ended there: https://lists.openembedded.org/g/openembedded-core/topic/80577032#147978 I think this report should eventually be closed or at least removed from the newcomer bug list.
On the list: https://lists.openembedded.org/g/openembedded-core/topic/80577032#147978 Ross Burton said: > I understand that you're simply fixing a newcomer bug but I just don't > see the rationale behind the bug in the first place. Copying in > Robert for his opinion. > > I'm unaware of any real world limitations of INI files that are a > problem for runqemu. We either break compatibility with existing > builds, or have two separate parsing codepaths in runqemu which > complicates things more (as the ini path won't get tested). > > Ross so I'm closing this enhancement. If there's a clear need to support qemuboot.json, please feel free to explain and re-open.
Thanks to Guillaume for looking into this issue and poking me to close it.