From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v8] pkg-download: silence downloads if make is silent
Date: Thu, 1 Jan 2015 19:20:53 +0100 [thread overview]
Message-ID: <20150101182053.GH4360@free.fr> (raw)
In-Reply-To: <CAHkwnC9wB=BEBeyaWV1TV68MXBqjyoK7o7Px6FyfVwQ_cNpEGA@mail.gmail.com>
Fabio, All,
On 2015-01-01 19:14 +0100, Fabio Porcedda spake thusly:
> On Thu, Jan 1, 2015 at 7:08 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Fabio, All,
> >
> > On 2015-01-01 18:54 +0100, Fabio Porcedda spake thusly:
> >> On Thu, Jan 1, 2015 at 5:50 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> > From: Fabio Porcedda <fabio.porcedda@gmail.com>
> >> >
> >> > If it is a silent build (make -s -> QUIET=-q) silence all downloads, as
> >> > well as the check-hash. Only stdout is redirected, stderr is still
> >> > visible, for errors and warning.
> >>
> >> Hi Yann,
> >> nice idea, i tried this patch but even if it works for check-hash and
> >> svn it does not works for the git backend (e.g. libubox) and the wget
> >> bakend (try it without the QUIET flags in the WGET variable).
> >>
> >> I don't understand the reason for this behavior.
> >> Do you have an idea for this strange behavior?
> >
> > Ok, that's because git always sends its report status to stderr:
> >
> > --quiet, -q
> > Operate quietly. Progress is not reported to the standard
> > error stream. [...]
> >
> > So, we need to pass -q to git. Sigh, fscking borked behaviour... stderr
> > is for failures, not normal reporting... :-(
> So that's the reason...
>
> >
> > OK, so we need to pass -q to some backends.
> >
> > However, what I did not like in your original patch was the fact that
> > some backends were singled out in the wrapper script. We do not want
> > that, we want the wrapper to be backend-agnostic (that's the whole point
> > of having a wrapper and backends).
>
> Well that it's needed only until all backends support the "-q" flag,
> do you prefer a big patch to convert all backends so that check is not
> needed?
I'm already on it... ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-01-01 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 16:50 [Buildroot] [PATCH 0/2 v8] Improve silent builds (branch yem/fabio/silent) Yann E. MORIN
2015-01-01 16:50 ` [Buildroot] [PATCH 1/2 v8] Makefile: improve detection of make "-s" flag Yann E. MORIN
2015-01-01 16:50 ` [Buildroot] [PATCH 2/2 v8] pkg-download: silence downloads if make is silent Yann E. MORIN
2015-01-01 17:54 ` Fabio Porcedda
2015-01-01 17:58 ` Yann E. MORIN
2015-01-01 18:03 ` Fabio Porcedda
2015-01-01 18:08 ` Yann E. MORIN
2015-01-01 18:08 ` Yann E. MORIN
2015-01-01 18:14 ` Fabio Porcedda
2015-01-01 18:16 ` Fabio Porcedda
2015-01-01 18:20 ` Yann E. MORIN [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=20150101182053.GH4360@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