On Wed, 2021-10-20 at 09:09 +0000, Peter Kjellerstedt wrote:
> I thought of another problem with the wrapper class solution: if we need to
> actually backport a newer version of the class from, e.g., Poky master, then
> there is now no natural place for it since it is occupied by the wrapper
> class. That means we would either have to rename the backported class, or put
> it somewhere else than in “classes”. It also means backporting a class
> requires the wrapper class to be modified.
>  
> Here is a question for Richard: what do you think of an idea I had to add
> support in bitbake for extending classes? I do not mean to add something like
> bbclassappend, as I know that is troublesome. My idea instead is something
> like the prefuncs/postfuncs that we have for functions. I.e., before actually
> doing the inherit of a classfoo, bitbake would inherit anything specified
> inBBCLASS_PRE_INHERIT:foo, and after inheriting the class it would
> automatically inherit anything in BBCLASS_POST_INHERIT:foo.  That way one can
> simply extend a class through normal variable operations, making it easy to
> do, e.g., in the distro configuration.

That sounds very like a bbclassappend under a different name?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157256): 
https://lists.openembedded.org/g/openembedded-core/message/157256
Mute This Topic: https://lists.openembedded.org/mt/86444902/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to