13172 2019-02-05 20:59:45 +0000 Kernels with non-standard names don't provide virtual/kernel 2021-11-11 13:17:16 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 0.0.0 x86 Multiple RESOLVED FIXED Medium normal 4.0 M2 1 ross.burton bruce.ashfield randy.macleod richard.purdie tom.zanussi --- --- No (bug/feature does not impact docs) oldest_to_newest 82964 0 ross.burton 2019-02-05 20:59:45 +0000 We let kernel recipes name their packages something unique: kernel.bbclasss: KERNEL_PACKAGE_NAME ??= "kernel" But if the name isn't "kernel" then they don't provide virtual/kernel, so can't be really be used if all of the valid kernels have a name set: kernel.bbclasss: PROVIDES += "${@ "virtual/kernel" if (d.getVar("KERNEL_PACKAGE_NAME") == "kernel") else "" }" I believe that line should just be PROVIDES += "virtual/kernel". 82966 1 richard.purdie 2019-02-07 15:48:14 +0000 This is to allow multiple kernels to be built reusing the class code. We don't want two kernels to PROVIDE virtual/kernel so I'd say this is not a bug... 83881 2 bruce.ashfield 2019-05-22 20:53:00 +0000 We should decide on this in 2.8. Is it a bug or not. Having just been through all this code myself, I'm also inclined to say not a bug. 88664 3 bruce.ashfield 2020-11-23 18:09:07 +0000 Will start running tests with the simplest of changes and see if anything breaks. 91953 4 bruce.ashfield 2021-11-11 13:17:16 +0000 merged to oe-core (now we wait to see if some unaccounted for case fails).