Bug 6059

Summary: Add mechanism to define how class should be used
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: coreAssignee: Unassigned <unassigned>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Low CC: meta.mr.watcher, meta.watcher, randy.macleod, ross.burton
Version: 1.7   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Paul Eggleton 2014-03-27 15:11:41 UTC 
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.
Comment 1 Richard Purdie 2019-10-03 15:23:08 UTC 
I do have basics of some patches for this issue.
Comment 2 Ross Burton 2023-10-19 15:06:29 UTC 
oe-core f5c128008365e141082c129417eb72d2751e8045 split the classes into classes-global and classes-recipe.