From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] insane.bbclass: skip dev-deps QA checking for ptest package
Date: Sun, 12 Jul 2015 10:54:48 +0800 [thread overview]
Message-ID: <55A1D6F8.4010801@windriver.com> (raw)
In-Reply-To: <CAJTo0LbS0ReW+N3YL=TU+AzeGogrS++jxabp5_=ns_GxFtOC4g@mail.gmail.com>
On 07/11/2015 06:26 AM, Burton, Ross wrote:
>
> On 6 July 2015 at 11:01, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
> The ptest pkg such as perl-ptest may need .h, .so or other files in dev
> package to run test cases, so skipping dev-deps checkin for ptest
> package.
>
>
> Is this a common occurrence or is perl the first instance of this? This warning
> can be skipped with INSANE_SKIP_${PN}-ptest = "dev-deps", right?
I only know perl atm, I will try more.
// Robert
>
> Ross
prev parent reply other threads:[~2015-07-12 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 10:01 [PATCH 0/1] insane.bbclass: skip dev-deps QA checking for ptest package Robert Yang
2015-07-06 10:01 ` [PATCH 1/1] " Robert Yang
2015-07-10 22:26 ` Burton, Ross
2015-07-12 2:54 ` Robert Yang [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=55A1D6F8.4010801@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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