Re: [gentoo-dev] force verbose build log as per PMS policy?

[Doug Goldstein <cardoe@gentoo.org>]

On Fri, Aug 3, 2012 at 6:18 PM, hasufell <hasufell@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/01/2012 06:07 PM, Michał Górny wrote:
>> On Wed, 01 Aug 2012 13:13:43 +0200 hasufell <hasufell@gentoo.org>
>> wrote:
>>
>>> We already had a discussion about cmake-utils.eclass and forcing
>>> verbose build log for that which was approved:
>>> http://archives.gentoo.org/gentoo-dev/msg_ce7d33748936663e84a5463fbf7f4d39.xml
>>>
>>>
>>>
> Also we have bug https://bugs.gentoo.org/show_bug.cgi?id=384193 and
>>> https://bugs.gentoo.org/show_bug.cgi?id=379497
>>>
>>> I opened a tracker
>>> https://bugs.gentoo.org/show_bug.cgi?id=429308
>>>
>>> Some devs seem unsure about that or want to have a council vote
>>> on that https://bugs.gentoo.org/show_bug.cgi?id=429332
>>
>> PMS doesn't have such a thing as a 'policy'. Gentoo can have one,
>> and I believe that should be discussed per Gentoo policy.
>>
>
> So that would simply mean we add that information to the devmanual?
>
> Should I open a bug with a devmanual patch then?

FFS, do not spam base-system yet again with stuff that's in the
process of being discussed still. Additionally, this is something that
should be fixed on the EAPI/eclass level and NOT per package. Putting
EXTRA_ECONF="--disable-silent-rules" in EVERY package is epically
moronic. Make econf automatically use --disable-silent-rules.

-- 
Doug Goldstein