From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-user+bounces-132144-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1RYHkR-0000Km-OW
	for garchives@archives.gentoo.org; Wed, 07 Dec 2011 13:41:23 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 06A8921C1BC;
	Wed,  7 Dec 2011 13:41:12 +0000 (UTC)
Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181])
	by pigeon.gentoo.org (Postfix) with ESMTP id 58E0A21C12E
	for <gentoo-user@lists.gentoo.org>; Wed,  7 Dec 2011 13:39:46 +0000 (UTC)
Received: by ghbg18 with SMTP id g18so591057ghb.40
        for <gentoo-user@lists.gentoo.org>; Wed, 07 Dec 2011 05:39:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type;
        bh=MEWFt02dkdbKSWYpFaIL+1+cJRmDhuueUsp7SNog3KY=;
        b=ovPIJDV+3hpcu5dzbw6zVN7qcdfWiafXi1Q66F7ydOrtOyymWgG77McMxkfLNWh4IO
         OnCnqhh6sMSieLSueehLgik2Lcby0XZ2v2FXttewzWtKgw7rBvwGsaJlXWu98ee0OyBk
         wVrWEkszOabC6rUDdjhkmvFcb0xTfqGZuhBdI=
Received: by 10.236.192.233 with SMTP id i69mr27322860yhn.60.1323265185881;
        Wed, 07 Dec 2011 05:39:45 -0800 (PST)
Received: from [192.168.2.5] (adsl-98-95-109-157.jan.bellsouth.net. [98.95.109.157])
        by mx.google.com with ESMTPS id o50sm3164194yhl.9.2011.12.07.05.39.43
        (version=SSLv3 cipher=OTHER);
        Wed, 07 Dec 2011 05:39:44 -0800 (PST)
Message-ID: <4EDF6C9E.8020102@gmail.com>
Date: Wed, 07 Dec 2011 07:39:42 -0600
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111022 Firefox/7.0.1 SeaMonkey/2.4.1
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge ignoring -v switch
References: <20111203142348.GA17203@gaurahari.merseine.nu> <201112041518.57386.michaelkintzios@gmail.com> <20111204204955.3e8d101f@digimed.co.uk> <201112060858.43067.michaelkintzios@gmail.com> <20111207091428.0f610c7e@hactar.digimed.co.uk> <jbnevj$fi9$1@dough.gmane.org> <20111207105521.2b89d91e@digimed.co.uk> <CAA2qdGX01kGbwzpVxY5s_ehpLdG0QYu+LYCRzm=8FZdF1ry7qg@mail.gmail.com>
In-Reply-To: <CAA2qdGX01kGbwzpVxY5s_ehpLdG0QYu+LYCRzm=8FZdF1ry7qg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------010901000609080308070901"
X-Archives-Salt: 552657e4-9a7e-4afc-90c3-0f76dd7dec0b
X-Archives-Hash: 8f9d97eaf27267fb3d765539b5672280

This is a multi-part message in MIME format.
--------------010901000609080308070901
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Pandu Poluan wrote:
>
>
> On Dec 7, 2011 6:00 PM, "Neil Bothwick" <neil@digimed.co.uk 
> <mailto:neil@digimed.co.uk>> wrote:
> >
> > On Wed, 07 Dec 2011 12:26:12 +0200, Nikos Chantziaras wrote:
> >
> > > > Not only did I mean to finish it, I thought I had. Using 
> --jobs>1 sets
> > > > the quiet-build flag
> > >
> > > It also sets it if you don't use more than 1 job.  As another poster
> > > (Hinnerk) already mentioned, the only way to get the old behavior back
> > > is to use the "--quiet-build=n" option.
> >
> > What I said in the text that disappeared from the original post was that
> > --jobs has always hidden the gcc output, long before the quiet-build
> > option appeared. The new option only makes emerge behave the same when
> > -jobs is not set or set to 1.
> >
>
> Indeed, that change gave me a 'wtf moment' for awhile. I used --jobs, 
> and the one time I purposefully emerge using single job to debug a 
> failure... the output is still MIA. Luckily it wasn't an emergency so 
> I still had the mind to do 'man emerge'.
>
> At the very least, such changes that potentially produce a wtf moment 
> should be in the news. I mean, --as-needed has been in the news for 
> quite some time; --quiet-build should also get its own news dispatch.
>
> Rgds,
>

There will be a news item IF it stays with the current setting.  The 
news item will appear when it goes stable tho.  According to recent 
posts, it appears the council is going to discuss this and decide if it 
should be reverted or not.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"


--------------010901000609080308070901
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Pandu Poluan wrote:
    <blockquote
cite=3D"mid:CAA2qdGX01kGbwzpVxY5s_ehpLdG0QYu+LYCRzm=3D8FZdF1ry7qg@mail.gm=
ail.com"
      type=3D"cite">
      <p><br>
        On Dec 7, 2011 6:00 PM, "Neil Bothwick" &lt;<a
          moz-do-not-send=3D"true" href=3D"mailto:neil@digimed.co.uk">nei=
l@digimed.co.uk</a>&gt;
        wrote:<br>
        &gt;<br>
        &gt; On Wed, 07 Dec 2011 12:26:12 +0200, Nikos Chantziaras
        wrote:<br>
        &gt;<br>
        &gt; &gt; &gt; Not only did I mean to finish it, I thought I
        had. Using --jobs&gt;1 sets<br>
        &gt; &gt; &gt; the quiet-build flag<br>
        &gt; &gt;<br>
        &gt; &gt; It also sets it if you don't use more than 1 job. =C2=A0=
As
        another poster<br>
        &gt; &gt; (Hinnerk) already mentioned, the only way to get the
        old behavior back<br>
        &gt; &gt; is to use the "--quiet-build=3Dn" option.<br>
        &gt;<br>
        &gt; What I said in the text that disappeared from the original
        post was that<br>
        &gt; --jobs has always hidden the gcc output, long before the
        quiet-build<br>
        &gt; option appeared. The new option only makes emerge behave
        the same when<br>
        &gt; -jobs is not set or set to 1.<br>
        &gt;</p>
      <p>Indeed, that change gave me a 'wtf moment' for awhile. I used
        --jobs, and the one time I purposefully emerge using single job
        to debug a failure... the output is still MIA. Luckily it wasn't
        an emergency so I still had the mind to do 'man emerge'.</p>
      <p>At the very least, such changes that potentially produce a wtf
        moment should be in the news. I mean, --as-needed has been in
        the news for quite some time; --quiet-build should also get its
        own news dispatch.</p>
      <p>Rgds,<br>
      </p>
    </blockquote>
    <br>
    There will be a news item IF it stays with the current setting.=C2=A0=
 The
    news item will appear when it goes stable tho.=C2=A0 According to rec=
ent
    posts, it appears the council is going to discuss this and decide if
    it should be reverted or not.=C2=A0 <br>
    <br>
    Dale<br>
    <br>
    :-)=C2=A0 :-)=C2=A0 <br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
I am only responsible for what I said ... Not for what you understood or =
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS=3D"--quiet-build=3Dn"</pre>
  </body>
</html>

--------------010901000609080308070901--