On Tuesday 31 of January 2012, Norbert Thiebaud wrote:
One thing that would mitigate the size of the log in that case would
be to hide the 'untar' output, even in verbose mode
(put it is a separate file in misc/logs for instance)
un-tarring of boost, for instance, account for thousands of line of
pointless output in verbose mode...
even better, for gbuild, would be to store the output of each command
in a file (again logs/xxx) and only display it inn case of problem.
Or only display the command itself only in case of a problem. That would
avoid most of the unneeded output and still, I assume, would do and be an
optimal default.
--
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.