6059 2014-03-27 15:11:41 +0000 Add mechanism to define how class should be used 2023-10-19 15:06:29 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.7 All Multiple RESOLVED FIXED Low enhancement Future 1 bluelightning unassigned meta.mr.watcher meta.watcher randy.macleod ross.burton --- --- Yes (doc changes required) oldest_to_newest 41860 0 bluelightning 2014-03-27 15:11:41 +0000 Classes can be inherited globally or per-recipe, and some classes are suitable for one and not the other. We should have a way of identifying in the class when that is the case and showing a coherent error when the class is used incorrectly. (There are also standard classes that the system already inherits at the right point which the user should not try to inherit themselves.) This will require adding the mechanism and then adding the definitions to each class as appropriate. 85197 1 richard.purdie 2019-10-03 15:23:08 +0000 I do have basics of some patches for this issue. 96746 2 ross.burton 2023-10-19 15:06:29 +0000 oe-core f5c128008365e141082c129417eb72d2751e8045 split the classes into classes-global and classes-recipe.