IMAGE_FEATURES VS PACKAGEGROUP
Hi Members ,
I was unable to appreciate the exact difference and role to have these two entity separately. Below is my understanding, hence though to check with members to get the clearer picture
IMAGE_FEATURES : Acts like top level wrapper to have set of packages added in image implicitly
- By implicitly i mean which packages will be added is controlled by Yocto layer rather than user
PACKAGEGROUP : Acts like top level wrapper to have set of packages added in image explicitly
- By explicitly i mean which packages will be added is controlled by user
So in my understanding i have mapped IMAGE_FEATURES as "predefined yocto PACKAGEGROUP"
Can members please help to get the exact usage here
Thanks ,
Ashish
Quoted 6 lines · Ashish Mishra via lists.openembedded.org
I was unable to appreciate the exact difference and role to have these two entity separately. Below is my understanding, hence though to check with members to get the clearer picture
IMAGE_FEATURES: Acts like top level wrapper to have set of packages added in image implicitly
- By implicitly i mean which packages will be added is controlled by Yocto layer rather than user
Quoted 6 lines
PACKAGEGROUP : Acts like top level wrapper to have set of packages added in image explicitly
- By explicitly i mean which packages will be added is controlled by userSo in my understanding i have mapped
IMAGE_FEATURESas "predefined yocto PACKAGEGROUP"Can members please help to get the exact usage here
packagegroups are empty packages that only contain dependencies on other packages. They're defined with recipes, and otherwise behave like any other recipe, and packages produced by them can be added to the image in the same way as packages from regular recipes. They're beneficial when you want to group packages and install them as a set, without modifying image recipes directly. This scales better in maintenance of the product.
IMAGE_FEATURES are loosely defined as properties of the image. Some of those features indeed are about what gets installed (e.g. dev-pkgs), but others (e.g. read-only-rootfs) are about how the image as a whole is configured. You basically tell yocto: I want this feature in my image, please figure it out by installing what is needed and doing other tweaks.
Alex