Linux Test Project
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: Joerg Vehlow <lkml@jv-coder.de>
Cc: ltp@lists.linux.it, Joerg Vehlow <joerg.vehlow@aox.de>
Subject: Re: [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout
Date: Tue, 05 Jul 2022 08:37:11 +0100	[thread overview]
Message-ID: <87zghoq9km.fsf@suse.de> (raw)
In-Reply-To: <b33360f5-96ba-f7c3-9e86-f7966c260eb9@jv-coder.de>

Hello Joerg,

Joerg Vehlow <lkml@jv-coder.de> writes:

> Hi Richard,
>
> Am 7/5/2022 um 8:28 AM schrieb Richard Palethorpe:
>> 
>> Richard Palethorpe <rpalethorpe@suse.de> writes:
>> 
>>> Hello Joerg,
>>>
>>> Joerg Vehlow <lkml@jv-coder.de> writes:
>>>
>>>> From: Joerg Vehlow <joerg.vehlow@aox.de>
>>>>
>>>> This allows installation of the tests to a different directory
>>>> than directly under $prefix.
>>>>
>>>> Before the layout was:
>>>> $prefix/bin/{run-*,t0,run-tests.h,Makefile}
>>>> $prefix/conformance
>>>> $prefix/functional
>>>> $prefix/stress
>>>>
>>>> with prefix being /opt/openposix_testsuite on linux and
>>>> /usr/local/openposix_testsuite on other systems
>>>> OR the value of the env-var $prefix.
>>>>
>>>> With this change, the prefix defaults to /opt/openposix_testsuite
>>>> and can be changed the usual way using configure (./configure ---prefix=foo)
>>>> Additionally the path of the tests below $prefix can be changed, using
>>>> configure --with-open-posix-testdir=<foo>. This allows clean installation as
>>>> part of ltp:
>>>>
>>>> $prefix/bin/{run-all-posix-option-group-tests.sh,run-posix-option-group-test.sh}
>>>> $prefix/$testdir/bin/{run-tests.sh,t0}
>>>> $prefix/$testdir/conformance
>>>> $prefix/$testdir/functional
>>>> $prefix/$testdir/stress
>> 
>> Sorry I don't see the need for this. I can't find the RFC where you may
>> have explained it, however it should be written here anyway I think.
>
> here is the RFC in the mailing list archive:
> https://lists.linux.it/pipermail/ltp/2022-June/029188.html
>
> Joerg

OK, so things are being installed twice and it is generally a
mess. This looks like a good cleanup.

However this really needs to be explained in the patchset. There
needs to be a clear description of where things have moved from and
to. In particular what someone needs to do if this breaks their test
runner scripts. This can then be copied into the LTP release notes.

BTW IIRC we generate runtest files for the open posix tests and the test
runner handles them almost like normal LTP tests. We don't use any of
those scripts either.

-- 
Thank you,
Richard.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-07-05  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 12:53 [LTP] [0/3] openposix: Fix installation file layout Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-07-05  5:57   ` Richard Palethorpe
2022-07-05  6:28     ` Richard Palethorpe
2022-07-05  6:37       ` Joerg Vehlow
2022-07-05  7:37         ` Richard Palethorpe [this message]
2022-07-27  5:42           ` Joerg Vehlow
2022-07-05  6:43     ` Joerg Vehlow
2022-07-27  5:26     ` Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-05  6:22   ` Richard Palethorpe

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=87zghoq9km.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --cc=joerg.vehlow@aox.de \
    --cc=lkml@jv-coder.de \
    --cc=ltp@lists.linux.it \
    /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