Bug 9077

Summary: The creation of manifests is incomplete
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Igor Stoppa <igor.stoppa>
Component: deploymentAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, patrick.ohly, richard.purdie
Version: unspecified   
Target Milestone: 2.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Igor Stoppa 2016-02-08 15:28:48 UTC
When building an image, the recipe correctly builds the ....rootfs.manifest file, however it doesn't seem to account for the creation of the initramfs (when produced).
Comment 1 Paul Eggleton 2016-02-11 02:20:21 UTC
There should be a separate manifest for the initramfs, since the initramfs is effectively a separate image.
Comment 2 Igor Stoppa 2016-02-11 08:02:03 UTC
Yes, most of the recipes related to image creation make a lot of confusion between rootfs, partition, disk image, overloading the same concept.
This is just an example of what such confusion leads to.
Comment 3 Richard Purdie 2016-02-11 15:50:52 UTC
Reassign to Igor for more info. Paul is basically correct, we'd expect the system to give two manifests, one for each of the images.

I understand that this may not always be what the user wants, however I don't think we can always do exactly what the user might think and this behaviour is as its designed.

If there is a proposal about how the system could work such that the user can always get what they need we're open to that but personally, I can't see how it would work.

So please either put forward a proposal we could look at and work on, or we should resolve this as being working as designed.
Comment 4 Igor Stoppa 2016-02-11 15:58:50 UTC
I would propose to drop the "rootfs" part from the name.
That would seem the simpler way to deal with it.


Other option could be to have a combined manifest referring o the overall image, but it might be too complex to justify the effort.
Comment 5 Igor Stoppa 2016-03-04 13:20:47 UTC
Argh, sorry, Comment #4 was meant for a different issue, please ignore it or remove it if possible.
Comment 6 Igor Stoppa 2016-03-04 13:22:05 UTC
(In reply to comment #5)
> Argh, sorry, Comment #4 was meant for a different issue, please ignore it or
> remove it if possible.

No, it was actually this comment wrong. Time for a coffee :-(
Comment 7 Richard Purdie 2016-03-28 17:06:35 UTC
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=26ee4ddc653d97f5c436c66a8504493209e3c65e was merged which makes the prefix configurable and I believes resolves the issues mentioned here. Over time we can look at removing this but for now, it at least makes it configurable for cases where its confusing.