[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 User rt changed the following: What|Old value |New value Status|VERIFIED |CLOSED --- Additional comments from [EMAIL PROTECTED] Wed Jun 25 07:05:42 + 2008 --- closing - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 User rt changed the following: What|Old value |New value Status|NEW |STARTED --- Additional comments from [EMAIL PROTECTED] Thu Dec 13 08:23:44 + 2007 --- See also issue 84497 - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Tue Dec 11 15:15:05 + 2007 --- ->Rene: As said, I very much like what the Linux kernel does, it first looked unfamiliar but than provided some clear information what the system is currently doing focussing on the essentials. I suggest you just try it again, to get a feeling for it :-) Anyway, lets focus on the obvious stuff first, I can live with compiler command lines ... but mostly nothing else. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Fri Dec 7 16:19:52 + 2007 --- > So, let me say that I have a very _clear_ opinion on that. Me, too. > Let me give a short example. Ideally the action of compiling a C++ file is > only reported as progress, e.g.: > > compiling foo.cxx ... > > But, in case the action failed, it certainly needs to report the reason and > its context, e.g.: > > COMPILE ERROR #123 for foo.cxx: > g++ -I.. -I foo.cxx -o foo.o Uh, now. PLEASE not. That what the Linux kernel does and I *hate* it. Most of "normal" build systems *do* show the commands they run and they *should* for transparency. > IMHO, this verbosity thing is very important. This is what new developers see > the first time they start hacking on OOo. One or the other may remember how > Linux building looked like in the old days and how it got its verbosity under > control. We need to do the same. I disagree. (I presume you mean Linux building = Linux kernel building) What Linux does is the first time I change if I compile a Linux kernel by hand. I also maintain some stuff in Debian which does that and where I patches verbosity in again. I am at all for removing *unneeded* verbosity (deliver, "Executing shell macro", (maybe) tar xf*v*z but some info the compiler line showa *are* important (gcc-X.Y if overriden, defines getting properly passed etc). So *if* you want to decide to do what the kernel does, pleas discouple that with the rest. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Fri Dec 7 14:58:02 + 2007 --- Hi guys, seems that there are only vague opinions regarding verbosity. So, let me say that I have a very _clear_ opinion on that. _Every_ kind of verbosity not related to showing progress looks _unprofessional_! It creates the impression, that the author did not really know what he was doing, so he created verbosity for the purpose of controlling the build process. That certainly does not mean, that errors or warnings should be hidden. Au contraire, errors and warnings should ideally report the full reason for happening. This also means, that errors _must_ not be ignored and must be handled properly. And yes, I know that this is not as easy as it may sound. Let me give a short example. Ideally the action of compiling a C++ file is only reported as progress, e.g.: compiling foo.cxx ... But, in case the action failed, it certainly needs to report the reason and its context, e.g.: COMPILE ERROR #123 for foo.cxx: g++ -I.. -I foo.cxx -o foo.o You get what I mean. IMHO, this verbosity thing is very important. This is what new developers see the first time they start hacking on OOo. One or the other may remember how Linux building looked like in the old days and how it got its verbosity under control. We need to do the same. Sorry for being so verbose ... ;-) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Thu Dec 6 11:06:24 + 2007 --- since i expect reduced overall buildtime with reduced output (especially on windows watching tar -xv takes noticeable time), why not offer that by default? imho, a "beginer" will prefer speed over detailed output. and if someone likes to dive in deeper, the first step could be "how to enable detailed output?" ;) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Wed Dec 5 18:29:16 + 2007 --- I thought a bit about this and at the end, I do not have clear opinion on this 8) I'll always use verbose option myself anyway but do not want to force it for anyone... - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 --- Additional comments from [EMAIL PROTECTED] Wed Dec 5 14:45:18 + 2007 --- rt: my opinion: default to non-verbose. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 User rt changed the following: What|Old value |New value CC|'pjanik' |'fridrich_strba,hjs,kr,pja | |nik,rene' --- Additional comments from [EMAIL PROTECTED] Wed Dec 5 14:10:16 + 2007 --- I'd like to introduce a new variable for controlling build verbosity. Not only for deliver.pl, next step could be (optionally) removing 'v' option from untarring tarballs of external modules. Ause, Fridrich, Kay, Pavel, Rene, and others: what behaviour would you prefer? a) Have it quiet per default an get a 'verbose' configure option? b) Have it verbose as it has been up to now per default and get a 'quiet' option? (Which btw. would not really switch to a quiet build, just reduce verbosity.) I would like to get some opinions, whithout starting an endless thread in dev mailing list. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-issues] [Issue 84263] Make build verbosity confi gurable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84263 Issue #|84263 Summary|Make build verbosity configurable Component|tools Version|680 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|solenv Assigned to|rt Reported by|rt --- Additional comments from [EMAIL PROTECTED] Wed Dec 5 13:56:17 + 2007 --- CWS shutup1 introduced a -quiet option for deliver.pl. It also made that option default for deliver when called by build.pl as suggested in issue 79798. While some people like that default others prefer the old behaviour. Solution: make it dependent on an environment variable set by configure. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
