linux/meta-virtualization.git/classes/meta-virt-cfg.bbclass, branch masterMirror of git.yoctoproject.org/meta-virtualizationhttps://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master2020-02-10T15:28:38+00:00conf: defer DISTRO_FEATURE check to bbclass processing2020-02-10T15:28:38+00:00Bruce Ashfieldbruce.ashfield@gmail.com2020-02-10T15:27:56+00:00urn:sha1:3a7d446fa94787eda0bcc2f3759e07db5bda6b2f
We were using USER_CLASS loading to allow conditional checking
on DISTRO_FEATURES, which triggered distro feature specific version
pinning.
It was found that DISTRO_FEATURES set in local.conf is not
consistently available at layer.conf parse time, hence our checks
were not always working as expected (i.e. the version files are
not included).
If we move the DISTRO_FEATURE check to the bbclasses, and use it
to trigger the include, we should have a consistent set of variable
resolution and consistent behaviour.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
conf: fix meta-virt version / config include2019-12-06T18:51:57+00:00Bruce Ashfieldbruce.ashfield@gmail.com2019-12-06T18:51:57+00:00urn:sha1:b4dfe90a5e7a4fd1ac92f8c85ba852f9d28fea74
As was reported:
https://lists.yoctoproject.org/g/meta-virtualization/message/4173?p=,,,20,0,0,0::Created,,conf%2Flayer.conf+is+broken,20,2,0,61269733
The conditional include of the meta-virt versions and config was not
working properly due to parse time constraints.
This commit fixes that by following the example of the meta-cube layer
and instead using a user bbclass to load the .inc file after
distro/distro features have been resolved by bitbake.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>