From: alexander.kanavin@linux.intel.com
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Gary Thomas <gary@mlbassoc.com>
Subject: Re: sip.bbclass?
Date: Wed, 25 May 2016 16:04:56 +0300 (EEST) [thread overview]
Message-ID: <51142.10.252.8.31.1464181496.squirrel@linux.intel.com> (raw)
In-Reply-To: <1464159563.9570.90.camel@linuxfoundation.org>
> 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
prev parent reply other threads:[~2016-05-25 12:17 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 ` sip.bbclass? Richard Purdie
2016-05-25 13:04 ` alexander.kanavin [this message]
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=51142.10.252.8.31.1464181496.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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