Re: cmake-utils.eclass: set default of CMAKE_VERBOSE=1

On Fri, May 4, 2012 at 3:25 PM, Johannes Huber <[email protected]> wrote:
> Am Freitag, 4. Mai 2012, 14:41:42 schrieb Mike Gilbert:
>> On Fri, May 4, 2012 at 2:29 PM, hasufell <[email protected]> wrote:
>> > On 05/04/2012 08:00 PM, Johannes Huber wrote:
>> >> Am Freitag, 4. Mai 2012, 18:30:10 schrieb hasufell:
>> >>> # @ECLASS-VARIABLE: CMAKE_VERBOSE # @DESCRIPTION: # Set to enable
>> >>> verbose messages during compilation.
>> >>>
>> >>> By default this is deactivated which is inconvenient imo and
>> >>> results in pastes having minimum information. I have to tell
>> >>> users every time to recompile with CMAKE_VERBOSE=1 so that I have
>> >>> proper information on what is going on.
>> >>>
>> >>> Are there any arguments against this being default?
>> >>
>> >> In 95-99% of the build failures we get in kde herd the information
>> >> is sufficient. So from my point of view the current behaviour is
>> >> good.
>> >>
>> >> Greetings
>> >
>> > I think that as an argument pro CMAKE_VERBOSE=1 because that would
>> > cover 100% instead of 95-99.
>>
>> I only maintain a couple of cmake-based ebuilds, but I find having the
>> full compiler command line useful. Without it, I have to guess at what
>> was actually run.
>
> How about bump docs for that use case? For example
> http://www.gentoo.org/proj/en/qa/backtraces.xml
>

As far as I can tell, such documentation is largely ignored unless
users are pointed to it by a comment on a bug. It would be nice to
avoid having to wait for the user to respond with the updated build
log.