Our version one of image customisation functionality will show you a list of packages known to Toaster for a certain project, based on the information generated by builds. This approach has a problem: in a brand new project, the list of packages known can be very small. As an example, do the following: create a new project, and then build core-image-minimal. Then create a second project, and build core-image-minimal again. In the second project, create a custom image based on core-image-minimal. The list of packages will include only the 25 packages installed by core-image-minimal: nothing else. As a result, I will find no packages to add. Ideally, we should find a way of "bootstrapping" the package data, as we do for layers and recipes. What this actually means is hazy, but it could be something like an approximate list of packages produced by the openembedded-core layer for the machines provided by openembedded-core and meta-yocto-bsp. How we do this, I have no idea. The option discussed in the past was implementing a parsing process in Toaster, as explained on page 5 of this document https://wiki.yoctoproject.org/wiki/image/3/31/Image_customisation_in_Toaster.pdf An alternative would be enhancing the parsing process in the layer index to provide package information. Ideally, the parsing process would also provide us with package dependency information.