sip.bbclass?

sip.bbclass?

[Gary Thomas]

I was just wondering why sip.bbclass is in OE-core (at least
the Poky version master:c7e614c438706) when nothing uses it?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: sip.bbclass?

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]


> On May 25, 2016, at 8:34 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> 
> I was just wondering why sip.bbclass is in OE-core (at least
> the Poky version master:c7e614c438706) when nothing uses it?

OE-core can have components which are commonly used in OE infrastructure, especially bindings
may be checking all layers in layerindex would better answer your question
> 
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: sip.bbclass?

[Gary Thomas]

On 2016-05-25 08:13, Khem Raj wrote:
>
>> On May 25, 2016, at 8:34 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>
>> I was just wondering why sip.bbclass is in OE-core (at least
>> the Poky version master:c7e614c438706) when nothing uses it?
>
> OE-core can have components which are commonly used in OE infrastructure, especially bindings
> may be checking all layers in layerindex would better answer your question

My impression was [perhaps erroneously] that for an object to be
in OE-core, it had to be _needed_ by some other object in OE-core.
Many recipes have been migrated out when there was no longer a
use for them, so why not .bbclass files as well?  Most other
layers that need .bbclass files that aren't in OE-core just have
their own classes...

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: sip.bbclass?

[Richard Purdie]

On Wed, 2016-05-25 at 08:46 +0200, Gary Thomas wrote:
> On 2016-05-25 08:13, Khem Raj wrote:
> > 
> > > On May 25, 2016, at 8:34 AM, Gary Thomas <gary@mlbassoc.com>
> > > wrote:
> > > 
> > > I was just wondering why sip.bbclass is in OE-core (at least
> > > the Poky version master:c7e614c438706) when nothing uses it?
> > 
> > OE-core can have components which are commonly used in OE
> > infrastructure, especially bindings
> > may be checking all layers in layerindex would better answer your
> > question
> 
> My impression was [perhaps erroneously] that for an object to be
> in OE-core, it had to be _needed_ by some other object in OE-core.
> Many recipes have been migrated out when there was no longer a
> use for them, so why not .bbclass files as well?  Most other
> layers that need .bbclass files that aren't in OE-core just have
> their own classes...

Nothing in OE-Core uses extrenalsrc directly but we'd still want
something like that in the core so I don't think the rule is absolute.
What we wouldn't want to see is multiple layers maintaining different
and potentially incompatible versions of a class file.

That said, I think there are a few that we probably could clean up.

Cheers,

Richard

Re: sip.bbclass?

[alexander.kanavin]

> Nothing in OE-Core uses extrenalsrc directly but we'd still want
> something like that in the core so I don't think the rule is absolute.
> What we wouldn't want to see is multiple layers maintaining different
> and potentially incompatible versions of a class file.
>
> That said, I think there are a few that we probably could clean up.

As for sip.bblclass, nothing is using it in oe-core or meta-oe. So I just
removed it as a part of oe-core py3 patchset, because it's doing some
python 2 based magic, and I can't figure out what exactly without any
recipes to test with.

Alex