The current implementation of the agl-devel feature to enable developer support has a few issues:
It is defined in the metadata as a distro feature, which is high impact with respect to the sstate in Yocto. It should likely be shifted to using AGL_FEATURES as has been done with some of the other features.
The attached configuration changes touch some IMAGE variables at a global level, which likely has fallout for downstream attempts to do builds involving initramfs or other images or when using multiconfigs.
There are quite a few places where agl-devel is used to drive adding packages to a packagegroup. These pretty much all need to be removed to make doing a binary packagefeed more feasible, and doing so would also help with respect to sstate management in general.
Environment
None
Activity
Scott Murray
February 21, 2025 at 7:20 PM
This is still not fully resolved, so I would prefer to keep it open and try resolving for Trout.
The current implementation of the agl-devel feature to enable developer support has a few issues:
It is defined in the metadata as a distro feature, which is high impact with respect to the sstate in Yocto. It should likely be shifted to using AGL_FEATURES as has been done with some of the other features.
The attached configuration changes touch some IMAGE variables at a global level, which likely has fallout for downstream attempts to do builds involving initramfs or other images or when using multiconfigs.
There are quite a few places where agl-devel is used to drive adding packages to a packagegroup. These pretty much all need to be removed to make doing a binary packagefeed more feasible, and doing so would also help with respect to sstate management in general.