public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 2/2] doc: Add user-guide.txt
Date: Thu, 3 Oct 2019 18:43:48 +0200	[thread overview]
Message-ID: <20191003164347.GA2061@dell5510> (raw)
In-Reply-To: <20191003114428.GC1858@rei>

Hi Cyril,

> >  ```
> > -$ LTPROOT=/opt/ltp PATH="$PATH:$LTPROOT/testcases/bin" testcases/bin/wc01.sh
> > +$ LTPROOT=/opt/ltp PATH="$PATH:$LTPROOT/bin:$LTPROOT/testcases/bin" testcases/bin/wc01.sh
> >  ```

> This looks like an unrelated change at best and should probably be part
> of a separate patch.

> Also the only thing that seems to be installed in $LTPROOT/bin/ that
> could be potentially used by tests is the ffsb tool, that we are going
> to get rid anyways. So I would have avoided including it in the example
> anyways.

Yep, I'm aware ffsb is needed from $LTPROOT/bin. I haven't forced to send
proposal about ffbs adding into separate repository, that why I included it.
But sure, I'll drop this part.
Ack the rest?

> > +1. Library environment variables
> > +--------------------------------
> > +
> > +|==============================================================================
> > +| 'KCONFIG_PATH'        | The path to the kernel config file, (if not set, it tries
> > +                          the usual paths '/boot/config-RELEASE' or '/proc/config.gz').
> > +| 'LTPROOT'             | Prefix for installed LTP, the default is '/opt/ltp'.
> > +| 'LTP_COLORIZE_OUTPUT' | Force colorized output behaviour. 'y' or '1': always colorize
> > +                          'n' or '0': never colorize.
> > +| 'LTP_TIMEOUT_MUL'     | Multiply timeout, must be number >= 1 (> 1 is useful for
> > +                          slow machines to avoid unexpected timeout).
> > +                          Variable is also used in shell tests.
> > +| 'PATH'                | It's required to addjust path:
> > +                          `PATH="$PATH:$LTPROOT/bin:$LTPROOT/testcases/bin"`
+ off course to fix it here.
                               `PATH="$PATH:$LTPROOT/testcases/bin"`

> > +| 'TMPDIR'              | Base directory for template directory, which is required by C tests


Kind regards,
Petr

  reply	other threads:[~2019-10-03 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 11:58 [LTP] [RFC PATCH 0/2] Update user related docs Petr Vorel
2019-09-30 11:58 ` [LTP] [RFC PATCH 1/2] doc: Removed outdated ltp-howto.{txt,lyx} Petr Vorel
2019-10-03 11:35   ` [LTP] [RFC PATCH 1/2] doc: Removed outdated ltp-howto.{txt, lyx} Cyril Hrubis
2019-09-30 11:58 ` [LTP] [RFC PATCH 2/2] doc: Add user-guide.txt Petr Vorel
2019-10-03 11:44   ` Cyril Hrubis
2019-10-03 16:43     ` Petr Vorel [this message]
2019-10-04 13:21       ` Cyril Hrubis
2019-10-04 17:05         ` Petr Vorel

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=20191003164347.GA2061@dell5510 \
    --to=pvorel@suse.cz \
    --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