On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote: > On Fri, Nov 18, 2022 at 03:04:29PM +0000, Richard Purdie wrote: > > > My concern is having multiple different file formats and data streams. > > It means we no longer have one definitive data mechanism but two, then > > the argument for people also shipping yaml and other files with recipes > > also becomes difficult. We'd also have people wanting to query from one > > to the other eventually. > > > > The real issue here seems to be that our data format (.bb) is > > struggling with some forms of data. I've therefore a preference for > > fixing that rather than encouraging working around it. > > For oeqa runtime tests I propose this json file. If tests have any > customization need they should use either image recipe variables or this > file format if recipe variables can't support the format. For other > alternatives I'd need pointers where to implement and what. ptests are > normal packages so they don't complicate this.
The key question this comes down to is can anyone suggest a syntax for including python data structures in our metadata (and/or json data)? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#173475): https://lists.openembedded.org/g/openembedded-core/message/173475 Mute This Topic: https://lists.openembedded.org/mt/95085492/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
