Hi Michael and Belen, I wanted to understand an aspect of workflow for image customization. This is what I understand so far.
1. You create a new project. 2. You see a list of image items you can add. The list is the initial best of what is available, and what the dependencies are. 3. You checkbox your initial set of choices, and you build the image target, and it runs. 4. You return to the list of image items. The list content and dependencies are now improved because bitbake/Toaster has much better information now that a build has been done. 5. You check and/or un-check your second pass set of choices, and you re-build the image target, and it runs. 6. You again return to the list of image items, make your third pass refinements, and re-build the image target. However, this time the image does not work, either because you removed too much functionally for your applications or because there was an error in the dependency data and the image is functionally inconsistent. 7. Here are my questions. * How do you recover to the last working configuration? * Do we recommend people to clone their projects (i.e. "Save-as") so that they have a backup? * Would we checkpoint the last (or last few) configurations so that they could do an undo? I ask because in our implementations of image customization the field engineers and customers almost always went to a point where the image failed, so having a recovery procedure was crucial for customer happiness. - David
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
