> I think that we should modify do_install_ptest_base to run
> do_install_ptest and install the Makefile irrespective of the presence
> of run-ptest file in ${WORKDIR}
> Something like:
> do_install_ptest_base() {
> if [ -f ${WORKDIR}/run-ptest ]; then
> install -D
On 28 September 2015, Tudor Florea wrote:
> > On 28 September 2015, Ross Burton wrote:
> > > 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.
>
On Tue, 2015-09-29 at 06:59 +, Ray, Ian (GE Healthcare) wrote:
> On 28 September 2015, Tudor Florea wrote:
> > > On 28 September 2015, Ross Burton wrote:
> > > > Surely if an upstream is under your control and is ptest-aware, it can
> > > > also
> > > > install run-ptest into the right place
On 29/09/2015 09:59, Ray, Ian (GE Healthcare) wrote:
On 28 September 2015, Tudor Florea wrote:
On 28 September 2015, Ross Burton wrote:
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
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) wrote:
The main benefit is for packages that are run-ptest /aware/, in which case
the recipe can be simplified.
Hi Tudor
On 28 September 2015, Tudor Florea wrote:
> On 9/21/2015 10:11, Ian Ray wrote:
>> Provides a new variable, PTEST_RUN_SCRIPT_PATH, which points to a
>> directory where the run-ptest script is located. This location
>> defaults to the work directory but may be overridden within a recipe
Hi Ross
> On 28 September 2015, Ross Burton wrote:
>> On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare)
>> 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
On 28 September 2015 at 15:46, Ray, Ian (GE Healthcare)
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
Hi Ian
On 9/21/2015 10:11, Ian Ray wrote:
> Provides a new variable, PTEST_RUN_SCRIPT_PATH, which points to a
> directory where the run-ptest script is located. This location
> defaults to the work directory but may be overridden within a recipe
> if a package ships its own run-ptest script.
>
Provides a new variable, PTEST_RUN_SCRIPT_PATH, which points to a
directory where the run-ptest script is located. This location
defaults to the work directory but may be overridden within a recipe
if a package ships its own run-ptest script.
Signed-off-by: Ian Ray
---
10 matches
Mail list logo