On Thu, 2017-07-20 at 18:43 -0400, Tom Rini wrote: > The support for writing vmdk/vdi/qcow2 images has not been converted to make > use of the IMAGE_CMD infrastructure and instead relies on custom logic for > adding tasks in the right place. Convert these images to making use of > IMAGE_CMD.
Thanks for working on this. I still have https://bugzilla.yoctoproject.org/show_bug.cgi?id=10204 open for enhancing vmdk/vdi/qcow2. However, your patch doesn't go as far as described in that bug, does it? Instead of allowing, for example, IMAGE_FSTYPES = "wic.vmdk", it merely changes how IMAGE_FSTYPES = "vmdk" is implemented. The current patch has its merits as it simplifies the implementation, but I think it would be worthwhile to go all the way, even if it changes how images are going to be named. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
