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 +0000 
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]

Reply via email to