7667 2015-04-27 23:05:33 +0000 Feature request: include expanded_data in the ConfigParsed event 2015-09-10 07:20:56 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED Medium enhancement 1.9 1 kergoth richard.purdie bluelightning bogdanx.a.voiculescu poky.bs.watcher poky.watcher georgex.l.musat --- --- Yes (doc changes required) oldest_to_newest 50540 0 kergoth 2015-04-27 23:05:33 +0000 The cooker now has finalized configuration metadata available, so we should consider including this metadata in the ConfigParsed event, as it's quite common to have to create our own copy of the metadata and finalize it in a ConfigParsed event handler. Also, expanded_data is not named well. Expansion isn't greatly relevant, other than of metadata keys. 50705 1 richard.purdie 2015-05-01 13:50:02 +0000 Since we're looking at trying to get rid of update_data entirely, I'm holding off this whilst we explore that... 52313 2 richard.purdie 2015-07-13 14:02:05 +0000 Since the data store changes merged, this is now resolved as the data store doesn't have to be expanded (http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a730981b75ebb528e447eb3e41c83440dbc133bd).