From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: sip.bbclass?
Date: Wed, 25 May 2016 07:59:23 +0100 [thread overview]
Message-ID: <1464159563.9570.90.camel@linuxfoundation.org> (raw)
In-Reply-To: <57454A49.7030700@mlbassoc.com>
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
next prev parent reply other threads:[~2016-05-25 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 5:34 sip.bbclass? Gary Thomas
2016-05-25 6:13 ` sip.bbclass? Khem Raj
2016-05-25 6:46 ` sip.bbclass? Gary Thomas
2016-05-25 6:59 ` Richard Purdie [this message]
2016-05-25 13:04 ` sip.bbclass? alexander.kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1464159563.9570.90.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox