From: Tudor Florea <tudor.florea@enea.com>
To: "Ray, Ian (GE Healthcare)" <ian.ray@ge.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto][PATCH 1/1] ptest: user-specified run-ptest script location
Date: Mon, 28 Sep 2015 21:44:57 +0300 [thread overview]
Message-ID: <56098AA9.2070505@enea.com> (raw)
In-Reply-To: <30E719D66AEA914CBB7DAB303B1C722D17290A@BUDURBPA11.e2k.ad.ge.com>
On 28.09.2015 18:41, Ray, Ian (GE Healthcare) wrote:
> Hi Ross
>
>> On 28 September 2015, Ross Burton wrote:
>>> On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare) <ian.ray@ge.com> wrote:
>>> The main benefit is for packages that are run-ptest /aware/, in which case
>>> the recipe can be simplified.
>> Surely if an upstream is under your control and is ptest-aware, it can also install run-ptest into the right place too?
> The run-ptest script is currently required to be in WORKDIR.
Actually run-ptest is currently required to be present in
/usr/lib/<package>/ptest. If a package is "ptest-aware", that package
should contain a install-ptest make target which will take care of
installing the run-ptest file.
> Can a package
> know WORKDIR without other changes to the recipe? (WORKDIR did not
> seem to be present in a quick check of a run.do_compile log I had handy.)
>
next prev parent reply other threads:[~2015-09-28 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:11 [yocto][PATCH 0/1] new PTEST_RUN_SCRIPT_PATH Ian Ray
2015-09-21 7:11 ` [yocto][PATCH 1/1] ptest: user-specified run-ptest script location Ian Ray
2015-09-28 13:49 ` Tudor Florea
2015-09-28 14:46 ` Ray, Ian (GE Healthcare)
2015-09-28 15:23 ` Burton, Ross
2015-09-28 15:41 ` Ray, Ian (GE Healthcare)
2015-09-28 18:44 ` Tudor Florea [this message]
2015-09-29 6:59 ` Ray, Ian (GE Healthcare)
2015-09-29 13:17 ` Richard Purdie
2015-09-29 19:53 ` Tudor Florea
2015-09-30 10:35 ` Ray, Ian (GE Healthcare)
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=56098AA9.2070505@enea.com \
--to=tudor.florea@enea.com \
--cc=ian.ray@ge.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