| Summary: | The creation of manifests is incomplete | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Igor Stoppa <igor.stoppa> |
| Component: | deployment | Assignee: | 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
There should be a separate manifest for the initramfs, since the initramfs is effectively a separate image. 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. 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. 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. Argh, sorry, Comment #4 was meant for a different issue, please ignore it or remove it if possible. (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 :-( 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. |