Bug 10133 - uninative tarball should contain layer manifest
Summary: uninative tarball should contain layer manifest
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 4.1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-08-12 14:04 UTC by Ross Burton
Modified: 2022-06-11 10:20 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2016-08-12 14:04:01 UTC 
It would be very useful if the uninative tarball contained the layer manifest that was used to build it, so we could know for sure what oe-core revision was used.
Comment 1 Bill Randle 2016-08-18 18:13:55 UTC 
Is there an existing script or bitbake invocation to create the layer manifest file?
Comment 2 Richard Purdie 2022-06-09 11:42:07 UTC 
This ended up being a bit of a rabbit hole but I've a patch on list to extend image-buildinfo to cover SDKs. Once we do that, we should be able to use it to include revision info in buildtools and uninative.