Bug 6059 - Add mechanism to define how class should be used
Summary: Add mechanism to define how class should be used
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.7
Hardware: All Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-27 15:11 UTC by Paul Eggleton
Modified: 2023-10-19 15:06 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.