Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4 v2] tools: add a directory to contain usefull user-facing tools
Date: Sun, 18 Jun 2017 16:23:24 +0200	[thread overview]
Message-ID: <20170618142324.GS2918@scaer> (raw)
In-Reply-To: <20170618161531.762b0929@windsurf>

Thomas, All,

On 2017-06-18 16:15 +0200, Thomas Petazzoni spake thusly:
> On Sun, 18 Jun 2017 16:01:40 +0200, Yann E. MORIN wrote:
> > Currently, we provide a few user-facing utilities, like get-developers,
> > in support/scripts/ . But this directory also contains internal scripts
> > that a user should not be directly concerned with. Besides, it is
> > two-level deep in the hierarchy, which is not really nice.
> > 
> > So, we introduce tools/ as a top-level directory, with the goal to store
> > and expose all user-facing utilities, while keeping our internal scripts
> > in support/scripts/ .
> > 
> > The first patch in the series introduces a new utility, brmake, a
> > wrapper around make that stores all the output to a log file and
> > displays only the >>> lines.
> > 
> > The second and subsequent patches each move a few user-facing utilities
> > out of support/scripts/ and into tools/ .
> 
> I am wondering if there is a very clear cut boundary between
> user-facing tools and non-user facing tools.

Yes, the frontier is not trivial.

I'd say that if a tool is meant to be called by the user, then it
belongs to tools/. If it is not meant to be alled by a user (even if it
could be so) then it belongs to support/scripts/.

> For example, graph-build-time or graph-depends are internally used by
> the Buildroot Makefile, but may also be used directly.

The primary use for those scripts is still an internal use. They are
supposed to be called from our infra.

> The size-stats
> tool is also used internally by the Buildroot Makefile, but
> size-stats-compare is meant to be used directly.

Then the former stays in support/scripts/ while the latter should move
to tools/.

> What about support/scripts/genimage.sh ?

I would leave it to support/scripts/. It is an internal helper./
Besides, it needs a few of our variables (TARGET_DIR and BINARIES_DIR),
so I see it as internal.

Of course, I might not have moved all that can/should be moved. This
series serves as a base for further discussion.

See the initial submission:

    [PATCH] contrib: add a directory to store "contrib" stuff
    http://lists.busybox.net/pipermail/buildroot/2016-October/174238.html

Regards,
Yann E. MORIN.

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

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-06-18 14:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 14:01 [Buildroot] [PATCH 0/4 v2] tools: add a directory to contain usefull user-facing tools Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 1/4 v2] tools: add a directory to store some useful " Yann E. MORIN
2017-06-19  1:11   ` Ricardo Martincoski
2017-06-19 15:42     ` Yann E. MORIN
2017-06-21  2:06       ` Ricardo Martincoski
2017-06-21  5:21         ` Yann E. MORIN
2017-06-21 21:44           ` Arnout Vandecappelle
2017-06-22 19:18             ` Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 2/4 v2] tools: move test-pkg out of support/scripts Yann E. MORIN
2017-06-18 14:12   ` Thomas Petazzoni
2017-06-18 14:16     ` Yann E. MORIN
2017-06-22  7:57     ` Arnout Vandecappelle
2017-06-22  8:13       ` Thomas Petazzoni
2017-06-22  8:30         ` Arnout Vandecappelle
2017-06-22 19:20           ` Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 3/4 v2] tools: move get-developers out of support/scripts/ Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 4/4 v2] tools: move check-package " Yann E. MORIN
2017-06-19  1:13   ` Ricardo Martincoski
2017-06-19 18:46     ` Yann E. MORIN
2017-06-19  3:22   ` Ricardo Martincoski
2017-06-19 18:48     ` Yann E. MORIN
2017-06-19 20:27       ` Ricardo Martincoski
2017-06-18 14:15 ` [Buildroot] [PATCH 0/4 v2] tools: add a directory to contain usefull user-facing tools Thomas Petazzoni
2017-06-18 14:23   ` Yann E. MORIN [this message]
2017-06-21 22:04     ` Arnout Vandecappelle

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=20170618142324.GS2918@scaer \
    --to=yann.morin.1998@free.fr \
    --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