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 1/6] support/scripts: add script to test a package
Date: Thu, 9 Feb 2017 23:00:37 +0100	[thread overview]
Message-ID: <20170209220037.GE3709@free.fr> (raw)
In-Reply-To: <20170209225033.5b7a5868@free-electrons.com>

Thomas, All,

On 2017-02-09 22:50 +0100, Thomas Petazzoni spake thusly:
> For some reason only your cover letter had PATCHv3, not the patches
> themselves. Could you check what happened?

Yup, I'll check...

> On Wed,  8 Feb 2017 21:15:24 +0100, Yann E. MORIN wrote:
> > This script helps in testing that a package builds fine on a wide range
> > of architectures and toolchains: BE/LE, 32/64-bit, musl/glibc/uclibc...
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > [yann.morin.1998 at free.fr:
> >  - completely rewrite the script from Thomas, with help from Luca
> > ]
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Luca Ceresoli <luca@lucaceresoli.net>
> > Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
> > Acked-by: Luca Ceresoli <luca@lucaceresoli.net>
> > Reviewed-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> 
> First of all, thanks for taking over my initial crappy submission and
> making it something production ready. I've applied your patch, but I
> nonetheless have a few comments about it. See below.
> 
> > +    opts="$( getopt -n "${my_name}" -o "${o}" -l "${O}" -- "${@}"  )"
> 
> I continue to terribly dislike this whole concept of putting a space
> after an opening parenthesis and before a closing parenthesis.
> 
> I know this is your coding style, but it is *not* the Buildroot coding
> style. So I'd appreciate if the shell scripts could also comply with
> the Buildroot coding style on this.

Fair enough. I'll post a patch fixing this.

> > +    printf "download config"
> 
> I find all these prints to be really useless, and they clutter the
> output for nothing. My original script had a very lean and readable
> output:
> 
> 	<toolchain>:	<status>
> 
> and now it's the much more verbose (and useless):
> 
>                 armv5-ctng-linux-gnueabi: download config, olddefconfig, build: OK
>               armv7-ctng-linux-gnueabihf: download config, olddefconfig, build: OK
> 
> (which would get even more verbose if I had passed a -p option, since
> dirclean would have been added).
> 
> I'd really prefer if we got rid of those additional prints, they are
> not useful, and make the whole thing less readable.

Well, I like that there is so feedback of what's going on under the
hood...

But I'll send updates to 'fix' that.

Thanks! :-)

Regards,
Yann E. MORIN.

> Thanks!
> 
> 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-02-09 22:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 20:15 [Buildroot] [PATCH 0/6 v3] support: script to build-test packages Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 1/6] support/scripts: add script to test a package Yann E. MORIN
2017-02-08 22:00   ` Cam Hutchison
2017-02-08 22:39     ` Cam Hutchison
2017-02-11 16:08     ` Yann E. MORIN
2017-02-11 21:19       ` Thomas De Schampheleire
2017-02-11 22:28         ` Yann E. MORIN
2017-02-09 13:41   ` Luca Ceresoli
2017-02-09 21:50   ` Thomas Petazzoni
2017-02-09 22:00     ` Yann E. MORIN [this message]
2017-02-09 21:51   ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 2/6] support/test-pkg: store lines missing from resulting configuraiton Yann E. MORIN
2017-02-09 17:07   ` Luca Ceresoli
2017-02-09 21:58   ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 3/6] support/test-pkg: report number and types of failures Yann E. MORIN
2017-02-09 17:09   ` Luca Ceresoli
2017-02-09 21:59   ` Thomas Petazzoni
2017-02-11 19:48     ` Thomas De Schampheleire
2017-02-11 22:21       ` Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 4/6] supprt/test-pkg: add option to limit the number of tests Yann E. MORIN
2017-02-09 22:13   ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 5/6] support/test-pkg: add option to use an alternate list of toolchains Yann E. MORIN
2017-02-11 19:53   ` Thomas De Schampheleire
2017-02-11 22:24     ` Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 6/6] support/test-pkg: print number of toolchain and progress Yann E. MORIN
2017-02-11 20:09   ` Thomas De Schampheleire
2017-02-11 22:25     ` Yann E. MORIN
2017-02-12  6:40       ` Thomas De Schampheleire
2017-02-12  9:33         ` Yann E. MORIN

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=20170209220037.GE3709@free.fr \
    --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