Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?

This is a bug: http://www.openoffice.org/issues/show_bug.cgi?id=102854 --Joachim Rony G. Flatscher wrote: Hi there, experimenting with OOo 3.2's unopkg.exe (under WindowsXP, SP3) it seems, that the output from unopkg.exe is only directed at stdout, whereas under Linux error messages (like

Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?

On 2010-03-20 19:37, rony wrote: Hi Oliver, On 20.03.2010 17:29, Oliver Brinzing wrote: you can use: unopkg add myExtension.oxt--shared --verbose --log-file c:\mylog.txt but this won't log error's (http://qa.openoffice.org/issues/show_bug.cgi?id=79831), output is: ## Progress log

[dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?

Hi there, experimenting with OOo 3.2's unopkg.exe (under WindowsXP, SP3) it seems, that the output from unopkg.exe is only directed at stdout, whereas under Linux error messages (like given package not installed and the like) are directed to stderr, and normal messages to stdout. Is this

Re: [dev] Windows' unopkg.exe does not differentiate between stderr and stdout, where does stdout go to when piping ?

Hi Rony, you can use: unopkg add myExtension.oxt--shared --verbose --log-file c:\mylog.txt but this won't log error's (http://qa.openoffice.org/issues/show_bug.cgi?id=79831), output is: ## Progress log entry 2010-03-20 16:54:33 ## Copying: myExtension.oxt Enabling:myExtension