Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Thursday 01 of December 2011, Norbert Thiebaud wrote:
On Wed, Nov 30, 2011 at 3:45 PM, Francois Tigeot <ftigeot@wolfpond.org> 
wrote:
None of the verbose build options documented in the wiki were working.
Having a clean non-verbose terminal output may be a pretty thing but if
it leads to lost hours of work, it's definitively _not_ an improvement.

 Uhm. The thing that lead to your lost hours of work was rather clearly the 
fact that you couldn't turn on the verbose output because of the incorrect 
wiki page. Not getting swamped by a lot of info that is useless in 99.9% 
cases _is_ an improvement.

 But I can buy the make default behaviour argument, although I still disagree. 
I'll at least add the make -s info to the build wiki page (make -r is worth 
mentioning there as well if not there yet, after all, it's not like 
plain 'make' command is a good default for LO build anyway).

It is not just a 'pretty' thing. it is also a chance to see warnings...
with a clean output they stick out clearly... otherwise you'd be hard
press to see them in that soup of 'command lines' echo.

 Not only warnings, also errors. Tinderbox mails are already pretty difficult 
to read as they are and anything that makes people less motivated to do more 
than just glance at them is bad. Thanks for switching tinderbox to -s.

-- 
 Lubos Lunak
 l.lunak@suse.cz

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.