I did something similar to this a while back, but I didn’t care about the image itself, just the manifest so I could generate RPM lists.
So we would install the base content from a tarball and then install supplemental / optional content from RPMs. I used a filter in my script to exclude the roots bootstrap components when I processed through the manifest. --- Regards, Darcy Darcy Watkins :: Senior Staff Engineer, Firmware SIERRA WIRELESS Direct +1 604 233 7989<tel:+1%20604%20233%207989> :: Fax +1 604 231 1109<tel:+1%20604%20231%201109> :: Main +1 604 231 1100<tel:+1%20604%20231%201100> 13811 Wireless Way :: Richmond, BC Canada V6V 3A4<x-apple-data-detectors://3/1> [M5] dwatk...@sierrawireless.com<mailto:dwatk...@sierrawireless.com> :: www.sierrawireless.com<http://www.sierrawireless.com/> On Jul 15, 2018, at 12:24 PM, Lukasz Zemla <lukasz.ze...@woodward.com<mailto:lukasz.ze...@woodward.com>> wrote: Dear All, Because of some formal reasons, we would like to split our rootfs image into 2 parts: 1. base system - to be reused between different project variants, typical rootfs content. 2. application/data - less critical application, configuration, data, logs. How to generate in Yocto application/data image(2)? It is about generation of empty image containing only requested packages, like Package-A, Package-B... We tried following: inherit image IMAGE_FEATURES = "" DISTRO_FEATURES = "" IMAGE_INSTALL = " \ Package-A \ Package-B \ " IMAGE_FSTYPES = "ubi tar.gz" But it produces classical rootfs image with (unwanted): bin, boot, etc, lib... We'd prefer to have it built in an efficient way, so we'd like to avoid generating full image and then removing files by hand in postprocess command. Thank you in advance, Lukasz ________________________________ *** The information in this email is confidential and intended solely for the individual or entity to whom it is addressed. If you have received this email in error please notify the sender by return e-mail, delete this email, and refrain from any disclosure or action based on the information. *** -- _______________________________________________ yocto mailing list yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7Cdwatkins%40sierrawireless.com%7C9a9853a61f09487bf9b208d5ea889416%7C08059a4c248643dd89e33a747e0dcbe8%7C1%7C0%7C636672794695866380&sdata=zMC3tfpRu9ukZP6o%2BYl0j9zRRE4apJJvbtZcWWx92Wg%3D&reserved=0
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
