Gentoo Archives: gentoo-dev

From: Francesco Riosa <vivo75@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] force verbose build log as per PMS policy?
Date: Wed, 01 Aug 2012 16:44:32
Message-Id: CAD6zcDxFUCiHCxxOW2dSHqPhN-MhPzRujz6DT9+W=H3Luy8koA@mail.gmail.com
In Reply to: [gentoo-dev] force verbose build log as per PMS policy? by hasufell
1 +1 for verbosity
2
3 Il giorno 01/ago/2012 13:21, "hasufell" <hasufell@g.o> ha scritto:
4 >
5 > We already had a discussion about cmake-utils.eclass and forcing verbose
6 > build log for that which was approved:
7 >
8 http://archives.gentoo.org/gentoo-dev/msg_ce7d33748936663e84a5463fbf7f4d39.xml
9 >
10 > Also we have bug https://bugs.gentoo.org/show_bug.cgi?id=384193 and
11 > https://bugs.gentoo.org/show_bug.cgi?id=379497
12 >
13 > I opened a tracker https://bugs.gentoo.org/show_bug.cgi?id=429308
14 >
15 > Some devs seem unsure about that or want to have a council vote on that
16 > https://bugs.gentoo.org/show_bug.cgi?id=429332
17 >
18 >
19 > When I sum that up again...
20 > - we are on gentoo and need as much information as possible for
21 > backtracing, resolving bugs, checking whether CFLAGS and such have been
22 > respected
23 > - no need to tell the user to recompile with
24 > EXTRA_ECONF="--disable-silent-rules" or similar just to be able to help
25 him
26 > - some QA checks might depend on verbose build log and are not yet
27 > implemented therefor
28 > - if people want nice build _output_ (not log), they can use --quiet-build
29 >