Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] ltp-testsuite: change install prefix
Date: Mon, 3 Oct 2016 23:27:56 +0200	[thread overview]
Message-ID: <20161003232756.10de67a8@free-electrons.com> (raw)
In-Reply-To: <1475322624-20518-1-git-send-email-nunes.erico@gmail.com>

Hello,

On Sat,  1 Oct 2016 13:50:22 +0200, Erico Nunes wrote:
> ltp-testsuite installs some of its files directly at its specified
> prefix, which by default in Buildroot is /usr for autotools packages.
> This is currently leaving scripts and its internal directories directly
> installed in /usr, such as in:
> 
>   # ls /usr
>   IDcheck.sh       lib64            runltplite.sh    share
>   Version          libexec          runtest          testcases
>   bin              runalltests.sh   sbin             testscripts
>   lib              runltp           scenario_groups  ver_linux
> 
> It also seems to be not feasible to try to install all of its testcases
> to standard locations such as /usr/bin as may contain hundreds of
> binaries and may not be able to find them all if we change their install
> locations. Therefore, it is better if ltp-testsuite installs its tree to
> its own self-contained subdirectory.
> Upstream instructions recommend that the install path be /opt/ltp,
> however it seems that installing things to /opt is not a very common
> Buildroot practice.
> The proposal then is to install it to /usr/lib/ltp-testsuite and so it
> can be run directly from there.
> 
> Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
> ---
> The /usr/lib/ltp-testsuite suggestion came from a brief discussion that
> I had on IRC about where would be the least bad place to install it.
> Alternatives could be /usr/share/ltp-testsuite or even /opt/ltp if we
> were to strictly follow the upstream documentation.
> It doesn't matter too much really as long as it doesn't mess /usr up
> anymore.
> ---
>  package/ltp-testsuite/ltp-testsuite.mk | 4 ++++
>  1 file changed, 4 insertions(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2016-10-03 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 11:50 [Buildroot] [PATCH 1/3] ltp-testsuite: change install prefix Erico Nunes
2016-10-01 11:50 ` [Buildroot] [PATCH 2/3] ltp-testsuite: bump to version 20160920 Erico Nunes
2016-10-03 21:37   ` Thomas Petazzoni
2016-10-08  4:14   ` Waldemar Brodkorb
2016-10-01 11:50 ` [Buildroot] [PATCH 3/3] ltp-testsuite: make Config.in libc comment standard Erico Nunes
2016-10-03 21:37   ` Thomas Petazzoni
2016-10-03 21:27 ` Thomas Petazzoni [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=20161003232756.10de67a8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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