As part of Developer story, Developer should be able to regenerate image out of published binary package feeds inside SDK environment. Developer also should be able to specify locally generated packages or repositories that can be added to the image.
There is some proof of concept for done for this with the imagebuilder code that is in my t222 poky-contrib branch. It sounds like we'd want to dust that off and use it. One question is whether we have to use the package feeds or whether sstate is available? I ask that since the sstate builds provide much better configuration validation than just building from package feeds. Our rootfs construction code also uses pkgdata during rootfs construction so as well as the package feeds, we also ideally need the pkgdata else the funcitonality would be more limited than from a main build.
sstate might be available, but not necesseraly. Developers should be able to use our package feeds, same as smart on the device. Plus they should be able to point to additional package repositories with 3rd party binary RPMs. Based on that, I don't think sstate would be really useful. In theory, information that is available to smart from RPM package repository meta-data should be more than enough to construct image based on package lists/groups definitions.
Is the "BUILD_IMAGES_FROM_FEEDS" feature working? Would it be usable for this case (or easily made usable)? Sstate would be provided for the "core" but not for 3rd party feeds.
So we've implemented the basic functionality using devtool and sstate; without using package feeds directly. I'm therefore marking this as resolved for 2.0 and we can open new bugs for additional functionality as needed.
Hello, This can be verified with devtool build-image some-image. (as per comment#4) I gave it a try on latest master: 505a82673ac2487df5ea343a6422c2fc47018831 on an Ubuntu machine. I tried devtool build-image core-image-minimal and worked fine. Marking as verified.