From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] manual: update old references to support/scripts
Date: Sat, 1 Jul 2017 18:40:40 +0200 [thread overview]
Message-ID: <20170701164041.5515-2-arnout@mind.be> (raw)
In-Reply-To: <20170701164041.5515-1-arnout@mind.be>
There were still some references to the old location of the scripts in
the manual. Replace them by utils/.
While we're at it, remove the redundant ./ at the beginning of some of
the example commands.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
---
docs/manual/adding-packages-python.txt | 8 ++++----
docs/manual/common-usage.txt | 2 +-
docs/manual/developers.txt | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/manual/adding-packages-python.txt b/docs/manual/adding-packages-python.txt
index a67a4bed4c..5eb6ba51b1 100644
--- a/docs/manual/adding-packages-python.txt
+++ b/docs/manual/adding-packages-python.txt
@@ -167,7 +167,7 @@ possible to customize what is done in any particular step:
If the Python package for which you would like to create a Buildroot
package is available on PyPI, you may want to use the +scanpypi+ tool
-located in +support/scripts+ to automate the process.
+located in +utils/+ to automate the process.
You can find the list of existing PyPI packages
https://pypi.python.org[here].
@@ -178,7 +178,7 @@ your host.
When at the root of your buildroot directory just do :
-----------------------
-./support/scripts/scanpypi foo bar -o package
+utils/scanpypi foo bar -o package
-----------------------
This will generate packages +python-foo+ and +python-bar+ in the package
@@ -198,7 +198,7 @@ If your Buildroot package is not in the official Buildroot tree but in
a br2-external tree, use the -o flag as follows:
-----------------------
-./support/scripts/scanpypi foo bar -o other_package_dir
+utils/scanpypi foo bar -o other_package_dir
-----------------------
This will generate packages +python-foo+ and +python-bar+ in the
@@ -207,7 +207,7 @@ This will generate packages +python-foo+ and +python-bar+ in the
Option +-h+ will list the available options:
-----------------------
-./support/scripts/scanpypi -h
+utils/scanpypi -h
-----------------------
[[python-package-cffi-backend]]
diff --git a/docs/manual/common-usage.txt b/docs/manual/common-usage.txt
index 8dd99a6dac..a22da20188 100644
--- a/docs/manual/common-usage.txt
+++ b/docs/manual/common-usage.txt
@@ -326,7 +326,7 @@ Buildroot release, use the +size-stats-compare+ script. It takes two
Refer to the help text of this script for more details:
----------------
-support/scripts/size-stats-compare -h
+utils/size-stats-compare -h
----------------
include::eclipse-integration.txt[]
diff --git a/docs/manual/developers.txt b/docs/manual/developers.txt
index 3c31aa96fa..4e2cd71638 100644
--- a/docs/manual/developers.txt
+++ b/docs/manual/developers.txt
@@ -26,7 +26,7 @@ to include in his patch the appropriate modification to the
The +DEVELOPERS+ file format is documented in detail inside the file
itself.
-The +get-developer+ tool, located in +support/scripts+ allows to use
+The +get-developer+ tool, located in +utils/+ allows to use
the +DEVELOPERS+ file for various tasks:
- When passing one or several patches as command line argument,
--
2.13.1
next prev parent reply other threads:[~2017-07-01 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 16:40 [Buildroot] [PATCH 1/3] DEVELOPERS: fix after moving scripts to utils/ directory Arnout Vandecappelle
2017-07-01 16:40 ` Arnout Vandecappelle [this message]
2017-07-01 16:50 ` [Buildroot] [PATCH 2/3] manual: update old references to support/scripts Yann E. MORIN
2017-07-01 16:40 ` [Buildroot] [PATCH 3/3] scancpan: update old reference " Arnout Vandecappelle
2017-07-01 16:51 ` Yann E. MORIN
2017-07-01 16:49 ` [Buildroot] [PATCH 1/3] DEVELOPERS: fix after moving scripts to utils/ directory Yann E. MORIN
2017-07-01 17:44 ` Thomas Petazzoni
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=20170701164041.5515-2-arnout@mind.be \
--to=arnout@mind.be \
--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