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-132143-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1RYFSj-0006kQ-Vp
for garchives@archives.gentoo.org; Wed, 07 Dec 2011 11:14:58 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 4982221C2EA;
Wed, 7 Dec 2011 11:14:49 +0000 (UTC)
Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212])
by pigeon.gentoo.org (Postfix) with ESMTP id 6079A21C268
for <gentoo-user@lists.gentoo.org>; Wed, 7 Dec 2011 11:13:27 +0000 (UTC)
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-MD5:128)
(Exim 4.69)
(envelope-from <pandu@poluan.info>)
id 1RYFRI-003PXv-LL
for gentoo-user@lists.gentoo.org; Wed, 07 Dec 2011 18:13:28 +0700
Received: by wgbds1 with SMTP id ds1so938069wgb.10
for <gentoo-user@lists.gentoo.org>; Wed, 07 Dec 2011 03:13:22 -0800 (PST)
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
Received: by 10.227.203.10 with SMTP id fg10mr14815096wbb.1.1323256402815;
Wed, 07 Dec 2011 03:13:22 -0800 (PST)
Received: by 10.223.103.70 with HTTP; Wed, 7 Dec 2011 03:13:22 -0800 (PST)
Received: by 10.223.103.70 with HTTP; Wed, 7 Dec 2011 03:13:22 -0800 (PST)
In-Reply-To: <20111207105521.2b89d91e@digimed.co.uk>
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>
Date: Wed, 7 Dec 2011 18:13:22 +0700
Message-ID: <CAA2qdGX01kGbwzpVxY5s_ehpLdG0QYu+LYCRzm=8FZdF1ry7qg@mail.gmail.com>
Subject: Re: [gentoo-user] Re: emerge ignoring -v switch
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=000e0cd59fe0d62a9e04b37ea31c
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com
X-AntiAbuse: Original Domain - lists.gentoo.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - poluan.info
X-Archives-Salt: 72df53aa-5bed-46a6-84bb-b01d689faebf
X-Archives-Hash: 44f2f446164408ef528f44f8a52d1974
--000e0cd59fe0d62a9e04b37ea31c
Content-Type: text/plain; charset=UTF-8
On Dec 7, 2011 6:00 PM, "Neil Bothwick" <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,
--000e0cd59fe0d62a9e04b37ea31c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p><br>
On Dec 7, 2011 6:00 PM, "Neil Bothwick" <<a href=3D"mailto:nei=
l@digimed.co.uk">neil@digimed.co.uk</a>> wrote:<br>
><br>
> On Wed, 07 Dec 2011 12:26:12 +0200, Nikos Chantziaras wrote:<br>
><br>
> > > Not only did I mean to finish it, I thought I had. Using --j=
obs>1 sets<br>
> > > the quiet-build flag<br>
> ><br>
> > It also sets it if you don't use more than 1 job. =C2=A0As an=
other poster<br>
> > (Hinnerk) already mentioned, the only way to get the old behavior=
back<br>
> > is to use the "--quiet-build=3Dn" option.<br>
><br>
> What I said in the text that disappeared from the original post was th=
at<br>
> --jobs has always hidden the gcc output, long before the quiet-build<b=
r>
> option appeared. The new option only makes emerge behave the same when=
<br>
> -jobs is not set or set to 1.<br>
></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 fa=
ilure... the output is still MIA. Luckily it wasn't an emergency so I s=
till had the mind to do 'man emerge'.</p>
<p>At the very least, such changes that potentially produce a wtf moment sh=
ould be in the news. I mean, --as-needed has been in the news for quite som=
e time; --quiet-build should also get its own news dispatch.</p>
<p>Rgds,<br>
</p>
--000e0cd59fe0d62a9e04b37ea31c--